path: root/init/Kconfig
diff options
authorPeter Zijlstra <>2008-02-13 15:45:39 +0100
committerIngo Molnar <>2008-02-13 15:45:39 +0100
commit23b0fdfc9299b137bd126e9dc22f62a59dae546d (patch)
tree22019172c555109b69a73da76561d99d7776c4f7 /init/Kconfig
parent4cf5d77a6eefaa7a464bc34e8cb767356f10fd74 (diff)
sched: rt-group: deal with PI
Steven mentioned the fun case where a lock holding task will be throttled. Simple fix: allow groups that have boosted tasks to run anyway. If a runnable task in a throttled group gets boosted the dequeue/enqueue done by rt_mutex_setprio() is enough to unthrottle the group. This is ofcourse not quite correct. Two possible ways forward are: - second prio array for boosted tasks - boost to a prio ceiling (this would also work for deadline scheduling) Signed-off-by: Peter Zijlstra <> Signed-off-by: Ingo Molnar <>
Diffstat (limited to 'init/Kconfig')
0 files changed, 0 insertions, 0 deletions