locking/rtmutex: Consolidate the fast/slowpath invocation
authorThomas Gleixner <tglx@linutronix.de>
Fri, 26 Mar 2021 15:29:41 +0000 (16:29 +0100)
committerIngo Molnar <mingo@kernel.org>
Mon, 29 Mar 2021 13:57:04 +0000 (15:57 +0200)
commit70c80103aafdeae99126694bc1cd54de016bc258
tree4ffef8a8f78ddf34e88a9d85435014656f855338
parentd7a2edb890c0bfe467140c0cd79fe7cf65249376
locking/rtmutex: Consolidate the fast/slowpath invocation

The indirection via a function pointer (which is at least optimized into a
tail call by the compiler) is making the code hard to read.

Clean it up and move the futex related trylock functions down to the futex
section.

Move the wake_q wakeup into rt_mutex_slowunlock(). No point in handing it
to the caller. The futex code uses a different function.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20210326153944.247927548@linutronix.de
kernel/locking/rtmutex.c