On Thu, 13 Apr 2017 22:02:54 +0800 Alex Shi <[email protected]> wrote:
> We don't need to adjust prio before new pi_waiter adding. The prio > only need update after pi_waiter change or task normal_prio change. > > Signed-off-by: Alex Shi <[email protected]> > Cc: Steven Rostedt <[email protected]> > Cc: Sebastian Siewior <[email protected]> > To: [email protected] > To: Ingo Molnar <[email protected]> > To: Peter Zijlstra <[email protected]> > Cc: Thomas Gleixner <[email protected]> > --- > kernel/locking/rtmutex.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c > index 05ff685..3ee8bc1 100644 > --- a/kernel/locking/rtmutex.c > +++ b/kernel/locking/rtmutex.c > @@ -973,7 +973,6 @@ static int task_blocks_on_rt_mutex(struct rt_mutex *lock, > return -EDEADLK; > > raw_spin_lock(&task->pi_lock); > - __rt_mutex_adjust_prio(task); Yeah, I'm not sure why this is called here. -- Steve > waiter->task = task; > waiter->lock = lock; > waiter->prio = task->prio;
