summaryrefslogtreecommitdiff
path: root/keymaps/toshiba-satellite_m30x
diff options
context:
space:
mode:
authorHolger Hans Peter Freyther <holger@moiji-mobile.com>2012-11-01 18:48:11 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2012-11-15 16:16:45 +0100
commitbb11271068ff34434f5b8cefd0c2c0bae5ed7fd1 (patch)
tree56195078c0c89146b7bf442d4569fe305ebc498f /keymaps/toshiba-satellite_m30x
parent71c015969233c21ea38b1e63993d02fe171df672 (diff)
sched: Only setting CPUSchedulingPriority=rr doesn't work
A service that only sets the scheduling policy to round-robin fails to be started. This is because the cpu_sched_priority is initialized to 0 and is not adjusted when the policy is changed. Clamp the cpu_sched_priority when the scheduler policy is set. Use the current policy to validate the new priority. Change the manual page to state that the given range only applies to the real-time scheduling policies. Add a testcase that verifies this change: $ make test-sched-prio; ./test-sched-prio [test/sched_idle_bad.service:6] CPU scheduling priority is out of range, ignoring: 1 [test/sched_rr_bad.service:7] CPU scheduling priority is out of range, ignoring: 0 [test/sched_rr_bad.service:8] CPU scheduling priority is out of range, ignoring: 100
Diffstat (limited to 'keymaps/toshiba-satellite_m30x')
0 files changed, 0 insertions, 0 deletions