349  * Deadlock detection is conditional:
351  * If CONFIG_DEBUG_RT_MUTEXES=n, deadlock detection is only conducted
354  * If CONFIG_DEBUG_RT_MUTEXES=y, deadlock detection is always
358  * deadlock detection is disabled independent of the detect argument
385  * Adjust the priority chain. Also used for deadlock detection.
390  * @chwalk:	do we have to carry out deadlock detection?
548 		 * If deadlock detection is off, we stop here if we  in rt_mutex_adjust_prio_chain()
549 		 * are not the top pi waiter of the task. If deadlock  in rt_mutex_adjust_prio_chain()
564 	 * deadlock detection is off, we stop the chain walk. If its  in rt_mutex_adjust_prio_chain()
594 	 * Deadlock detection. If the lock is the same as the original  in rt_mutex_adjust_prio_chain()
597 	 * walk, we detected a deadlock.  in rt_mutex_adjust_prio_chain()
607 	 * If we just follow the lock chain for deadlock detection, no  in rt_mutex_adjust_prio_chain()
633 		 * No requeue [11] here. We just do deadlock detection.  in rt_mutex_adjust_prio_chain()
780 	 * deadlock detection mode.  in rt_mutex_adjust_prio_chain()
939 	 * Early deadlock detection. We really don't want the task to  in task_blocks_on_rt_mutex()
942 	 * can come in before the chain walk detects the deadlock. So  in task_blocks_on_rt_mutex()
943 	 * the other will detect the deadlock and return -EDEADLOCK,  in task_blocks_on_rt_mutex()
944 	 * which is wrong, as the other waiter is not in a deadlock  in task_blocks_on_rt_mutex()
985 	 * Even if full deadlock detection is on, if the owner is not  in task_blocks_on_rt_mutex()
1209 	 * deadlock detection, nothing to do here.  in rt_mutex_handle_deadlock()
1731  * Starts the rt_mutex acquire; it enqueues the @waiter and does deadlock
1755 	/* We enforce deadlock detection for futexes */  in __rt_mutex_start_proxy_lock()
1780  * Starts the rt_mutex acquire; it enqueues the @waiter and does deadlock