From: Peter Zijlstra <peterz@infradead.org>
Date: Tue, 10 Nov 2009 19:12:01 +0000 (+0100)
Subject: sched: Make sure task has correct sched_class after policy change
X-Git-Tag: v2.6.33-rc1~398^2~18
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ffd44db5f02af32bcc25a8eb5981bf02a141cdab;p=pandora-kernel.git

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 <pwil3058@bigpond.net.au>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
LKML-Reference: <1257880321.4108.457.camel@laptop>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---

Reading git-diff-tree failed