diff options
| author | Peter Zijlstra <[email protected]> | 2009-11-10 20:12:01 +0100 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2009-11-10 20:22:31 +0100 |
| commit | ffd44db5f02af32bcc25a8eb5981bf02a141cdab (patch) | |
| tree | 75716dc543821a79a1dff0739b43bb0283d400cf /tools/perf/scripts/python/check-perf-trace.py | |
| parent | eae0c9dfb534cb3449888b9601228efa6480fdb5 (diff) | |
sched: Make sure task has correct sched_class after policy change
From the code in rt_mutex_setprio(), it is evident that the
intention is that task's with a RT 'prio' value as a consequence
of receiving a PI boost also have their 'sched_class' field set
to '&rt_sched_class'.
However, Peter noticed that the code in __setscheduler() could
result in this intention being frustrated. Fix it.
Reported-by: Peter Williams <[email protected]>
Signed-off-by: Peter Zijlstra <[email protected]>
Cc: Mike Galbraith <[email protected]>
LKML-Reference: <1257880321.4108.457.camel@laptop>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions