summaryrefslogtreecommitdiffstats
path: root/kernel/locking/mutex.c
diff options
context:
space:
mode:
authorAlex Shi <alex.shi@linaro.org>2017-07-13 14:18:24 +0800
committerIngo Molnar <mingo@kernel.org>2017-07-13 11:44:06 +0200
commit69f0d429c413fe96db2c187475cebcc6e3a8c7f5 (patch)
tree62d0f2cd136b5c2e191c01f5df8b3379ddab6526 /kernel/locking/mutex.c
parent5671360f29c68d9079914438f6a0109ef62f82a8 (diff)
downloadlinux-69f0d429c413fe96db2c187475cebcc6e3a8c7f5.tar.bz2
locking/rtmutex: Remove unnecessary priority adjustment
We don't need to adjust priority before adding a new pi_waiter, the priority only needs to be updated after pi_waiter change or task priority change. Steven Rostedt pointed out: "Interesting, I did some git mining and this was added with the original entry of the rtmutex.c (23f78d4a03c5). 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.shi@linaro.org> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Juri Lelli <juri.lelli@arm.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Sebastian Siewior <bigeasy@linutronix.de> Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/1499926704-28841-1-git-send-email-alex.shi@linaro.org [ Enhance the changelog. ] Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'kernel/locking/mutex.c')
0 files changed, 0 insertions, 0 deletions