We don't need to adjust prio before new pi_waiter adding. The prio
only need update after pi_waiter change or task priority change.
Steven Rostedt pointed:
"Interesting, I did some git mining and this was added with the original
entry of the rtmutex.c (23f78d4a0). Looking at even that version, I
don't see the purpose of adjusting the task prio here. It is done
before anything changes in the task."
Signed-off-by: Alex Shi <alex....@linaro.org>
Cc: Steven Rostedt <rost...@goodmis.org>
Cc: Sebastian Siewior <bige...@linutronix.de>
Cc: Mathieu Poirier <mathieu.poir...@linaro.org>
Cc: Juri Lelli <juri.le...@arm.com>
Cc: Thomas Gleixner <t...@linutronix.de>
To: linux-kernel@vger.kernel.org
To: Ingo Molnar <mi...@redhat.com>
To: Peter Zijlstra <pet...@infradead.org>
Reviewed-by: Steven Rostedt (VMware) <rost...@goodmis.org>
---
kernel/locking/rtmutex.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index 28cd09e..d1fe41f 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
@@ -963,7 +963,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);
waiter->task = task;
waiter->lock = lock;
waiter->prio = task->prio;
--
2.7.4
