openkylin
/
linux
mirror of https://gitee.com/openkylin/linux.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity

locking/rtmutex: Inline chainwalk depth check 

There is no point for this wrapper at all.

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/20210326153943.754254046@linutronix.de
This commit is contained in:
Thomas Gleixner 2021-03-26 16:29:36 +01:00 committed by Ingo Molnar
parent fae37feee0
commit f7efc4799f
1 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
kernel/locking/rtmutex.c
View File

@ -343,14 +343,9 @@ static void rt_mutex_adjust_prio(struct task_struct *p)
static bool rt_mutex_cond_detect_deadlock(struct rt_mutex_waiter *waiter, static bool rt_mutex_cond_detect_deadlock(struct rt_mutex_waiter *waiter,
enum rtmutex_chainwalk chwalk) enum rtmutex_chainwalk chwalk)
{ {
/* if (IS_ENABLED(CONFIG_DEBUG_RT_MUTEX))
* This is just a wrapper function for the following call, return waiter != NULL;
* because debug_rt_mutex_detect_deadlock() smells like a magic return chwalk == RT_MUTEX_FULL_CHAINWALK;
* debug feature and I wanted to keep the cond function in the
* main source file along with the comments instead of having
* two of the same in the headers.
*/
return debug_rt_mutex_detect_deadlock(waiter, chwalk);
} }
/* /*