tree 22019172c555109b69a73da76561d99d7776c4f7
parent 4cf5d77a6eefaa7a464bc34e8cb767356f10fd74
author Peter Zijlstra <a.p.zijlstra@chello.nl> 1202913939 +0100
committer Ingo Molnar <mingo@elte.hu> 1202913939 +0100

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 <a.p.zijlstra@chello.nl>
Signed-off-by: Ingo Molnar <mingo@elte.hu>