Home
last modified time | relevance | path

Searched refs:pi_blocked_on (Results 1 – 8 of 8) sorted by relevance

/linux-4.1.27/kernel/locking/
Drtmutex.c345 return p->pi_blocked_on ? p->pi_blocked_on->lock : NULL; in task_blocked_on_lock()
471 waiter = task->pi_blocked_on; in rt_mutex_adjust_prio_chain()
843 task->pi_blocked_on = NULL; in try_to_take_rt_mutex()
909 task->pi_blocked_on = waiter; in task_blocks_on_rt_mutex()
922 if (owner->pi_blocked_on) in task_blocks_on_rt_mutex()
1018 current->pi_blocked_on = NULL; in remove_waiter()
1073 waiter = task->pi_blocked_on; in rt_mutex_adjust_pi()
Drtmutex-debug.c61 DEBUG_LOCKS_WARN_ON(task->pi_blocked_on); in rt_mutex_debug_task_free()
Drtmutex-tester.c357 tsk->pi_blocked_on); in sysfs_test_status()
/linux-4.1.27/include/linux/sched/
Drt.h26 return tsk->pi_blocked_on != NULL; in tsk_is_pi_blocked()
/linux-4.1.27/kernel/
Dfork.c1208 p->pi_blocked_on = NULL; in rt_mutex_init_task()
/linux-4.1.27/include/linux/
Dsched.h1520 struct rt_mutex_waiter *pi_blocked_on; member
/linux-4.1.27/Documentation/locking/
Drt-mutex-design.txt758 We now clear the "pi_blocked_on" field of the new pending owner, and if
/linux-4.1.27/kernel/sched/
Dcore.c3022 WARN_ON(p->pi_blocked_on); in rt_mutex_setprio()