Home
last modified time | relevance | path

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

/linux-4.4.14/kernel/locking/
Drtmutex.c358 return p->pi_blocked_on ? p->pi_blocked_on->lock : NULL; in task_blocked_on_lock()
484 waiter = task->pi_blocked_on; in rt_mutex_adjust_prio_chain()
856 task->pi_blocked_on = NULL; in try_to_take_rt_mutex()
922 task->pi_blocked_on = waiter; in task_blocks_on_rt_mutex()
935 if (owner->pi_blocked_on) in task_blocks_on_rt_mutex()
1025 current->pi_blocked_on = NULL; in remove_waiter()
1080 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()
/linux-4.4.14/include/linux/sched/
Drt.h26 return tsk->pi_blocked_on != NULL; in tsk_is_pi_blocked()
/linux-4.4.14/kernel/
Dfork.c1212 p->pi_blocked_on = NULL; in rt_mutex_init_task()
/linux-4.4.14/include/linux/
Dsched.h1605 struct rt_mutex_waiter *pi_blocked_on; member
/linux-4.4.14/Documentation/locking/
Drt-mutex-design.txt758 We now clear the "pi_blocked_on" field of the new pending owner, and if
/linux-4.4.14/kernel/sched/
Dcore.c3390 WARN_ON(p->pi_blocked_on); in rt_mutex_setprio()