search for: sched_setscheduler

...<stdlib.h> #include <pthread.h> #include <sched.h> #include <errno.h> #include <unistd.h> void * dummy_worker(void *ptr) { printf("Hello from worker\n"); return NULL; } int main(void) { struct sched_param schedule; schedule.sched_priority = 50; if (sched_setscheduler(getpid(), SCHED_RR, &schedule) == 1) { perror("sched_setscheduler"); exit(EXIT_FAILURE); } cpu_set_t cpuset; CPU_ZERO(&cpuset); CPU_SET(1, &cpuset); if (sched_setaffinity(getpid(), sizeof(cpuset), &cpuset) == -1) { perror("sched_setaffinity")...

Dear all, I want to setup a privileged container, which means I can set the priority of a process to SCHED_RR (real-time) dynamically by calling sched_setscheduler() in a C program running on a container. In my system (host: fedora19, container: fedora19, libvirt 1.2.5), my C code reports "operation not permitted" when sched_setscheduler() is called. I found a link (https://www.redhat.com/archives/libvir-list/2014-June/msg00562.html) which is talkin...

Hi I was asking about the fedora 14 kernel if it is good enough for cgroup usage because I am trying to set a cgroup under cpu subsytem ( /dev/cgroup/cpu/group1/ ) that have /cpu.rt_runtime_us of 100000 while cpu.rt_period_us has a value of 1000000 i.e a ratio of 1/10 . still when I run a task (endless loop) in that group (cgexec -g cpu,cpuset:group1 ./test) it gets all the cpu core time

Does anyone have any ideas why my recently updated * 1.2.5 system should spawn multiple * process at seemingly random intervals? Regards L:ee ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/ -------------- next part -------------- An HTML attachment was scrubbed...

Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the

Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the

...quot; -DASTAGIDIR=\"/var/lib/asterisk/agi-bin\" -DBUSYDETECT_MARTIN -DNEW_PRI_HANGUP -c -o asterisk.o asterisk.c asterisk.c: In function `set_priority': asterisk.c:377: storage size of `sched' isn't known asterisk.c:384: warning: implicit declaration of function `sched_setscheduler' asterisk.c:384: `SCHED_RR' undeclared (first use in this function) asterisk.c:384: (Each undeclared identifier is reported only once asterisk.c:384: for each function it appears in.) asterisk.c:392: `SCHED_OTHER' undeclared (first use in this function) asterisk.c:377: warning: unused v...

Dear all, I want to run a process in a container with a real-time (RT) priority. When the sched_setscheduler(0, SCHED_RR, &sparam) is called in the container, an error is reported which is "operation not permitted" I had added the following line in the file /etc/security/limits.conf for both the host and the container, which means allowing all users to change the priority of the process, but...

The softlockup watchdog is currently a nuisance in a virtual machine, since the whole system could have the CPU stolen from it for a long period of time. While it would be unlikely for a guest domain to be denied timer interrupts for over 10s, it could happen and any softlockup message would be completely spurious. Earlier I proposed that sched_clock() return time in unstolen nanoseconds, which

The softlockup watchdog is currently a nuisance in a virtual machine, since the whole system could have the CPU stolen from it for a long period of time. While it would be unlikely for a guest domain to be denied timer interrupts for over 10s, it could happen and any softlockup message would be completely spurious. Earlier I proposed that sched_clock() return time in unstolen nanoseconds, which

...ank_work.work_list); > + init_waitqueue_head(&vblank->vblank_work.work_wait); > + > + vblank->vblank_work.thread = > + kthread_run(vblank_work_thread, vblank, "card %d crtc %d", > + vblank->dev->primary->index, vblank->pipe); > + > + ret = sched_setscheduler(vblank->vblank_work.thread, > + SCHED_FIFO, &param); > + WARN_ON(ret); > +} > + > +/** > + * drm_vblank_work_init - initialize a vblank work item > + * @work: vblank work item > + * @crtc: CRTC whose vblank will trigger the work execution > + * @func: work func...

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

...t;pending_work); + spin_lock_init(&vblank->work_lock); + vblank->worker = kthread_create_worker(0, "card%d-crtc%d", + vblank->dev->primary->index, + vblank->pipe); + if (IS_ERR(vblank->worker)) + return PTR_ERR(vblank->worker); + + return sched_setscheduler(vblank->worker->task, SCHED_FIFO, &param); +} + /** * drm_vblank_init - initialize vblank support * @dev: DRM device @@ -538,6 +578,10 @@ int drm_vblank_init(struct drm_device *dev, unsigned int num_crtcs) vblank); if (ret) return ret; + + ret = vblank_worker_ini...

...INIT_LIST_HEAD(&vblank->vblank_work.work_list); + init_waitqueue_head(&vblank->vblank_work.work_wait); + + vblank->vblank_work.thread = + kthread_run(vblank_work_thread, vblank, "card %d crtc %d", + vblank->dev->primary->index, vblank->pipe); + + ret = sched_setscheduler(vblank->vblank_work.thread, + SCHED_FIFO, &param); + WARN_ON(ret); +} + +/** + * drm_vblank_work_init - initialize a vblank work item + * @work: vblank work item + * @crtc: CRTC whose vblank will trigger the work execution + * @func: work function to be executed + * + * Initialize a vbla...

...k_lock); + init_waitqueue_head(&vblank->work_wait_queue); + worker = kthread_create_worker(0, "card%d-crtc%d", + vblank->dev->primary->index, + vblank->pipe); + if (IS_ERR(worker)) + return PTR_ERR(worker); + + vblank->worker = worker; + + return sched_setscheduler(vblank->worker->task, SCHED_FIFO, &param); +} + /** * drm_vblank_init - initialize vblank support * @dev: DRM device @@ -539,6 +629,10 @@ int drm_vblank_init(struct drm_device *dev, unsigned int num_crtcs) vblank); if (ret) return ret; + + ret = vblank_worker_ini...

...ALLS.def +++ b/usr/klibc/SYSCALLS.def @@ -47,6 +47,7 @@ int execve(const char *, char * const *, char * const *); <alpha,ia64> int getpriority(int, int); <!alpha,ia64> int getpriority::__getpriority(int, int); int setpriority(int, int, int); +int getrusage(int, struct rusage *); int sched_setscheduler(pid_t, int, const struct sched_param *); int sched_yield(); <i386> int prctl at varadic(int, unsigned long, unsigned long, unsigned long, unsigned long);

...>vblank_work.work_wait); > > > + > > > + vblank->vblank_work.thread = > > > + kthread_run(vblank_work_thread, vblank, "card %d crtc %d", > > > + vblank->dev->primary->index, vblank->pipe); > > > + > > > + ret = sched_setscheduler(vblank->vblank_work.thread, > > > + SCHED_FIFO, &param); > > > + WARN_ON(ret); > > > +} > > > + > > > +/** > > > + * drm_vblank_work_init - initialize a vblank work item > > > + * @work: vblank work item > > > + * @c...

...it_waitqueue_head(&vblank->vblank_work.work_wait); > > + > > + vblank->vblank_work.thread = > > + kthread_run(vblank_work_thread, vblank, "card %d crtc %d", > > + vblank->dev->primary->index, vblank->pipe); > > + > > + ret = sched_setscheduler(vblank->vblank_work.thread, > > + SCHED_FIFO, &param); > > + WARN_ON(ret); > > +} > > + > > +/** > > + * drm_vblank_work_init - initialize a vblank work item > > + * @work: vblank work item > > + * @crtc: CRTC whose vblank will trigger the...

...vblank->vblank_work.thread = > > > > + kthread_run(vblank_work_thread, vblank, "card %d crtc > > > > %d", > > > > + vblank->dev->primary->index, vblank- > > > > >pipe); > > > > + > > > > + ret = sched_setscheduler(vblank->vblank_work.thread, > > > > + SCHED_FIFO, &param); > > > > + WARN_ON(ret); > > > > +} > > > > + > > > > +/** > > > > + * drm_vblank_work_init - initialize a vblank work item > > > > + * @work: vbl...