Lines Matching refs:pi_lock

229 called pi_lock.  This lock may also be taken in interrupt context, so when
230 locking the pi_lock, interrupts must be disabled.
366 __rt_mutex_adjust_prio (same as the former, but expects the task pi_lock
433 was passed by parameter (for the first iteration).  The pi_lock of this task is
459 pi_lock and wait_lock goes in the opposite direction. If we fail to grab the
460 lock, the pi_lock is released, and we restart the loop.
462 Now that we have both the pi_lock of the task as well as the wait_lock of
466 Now we release the pi_lock of the task.
468 Next the owner of the mutex has its pi_lock taken, so we can update the
483 Lastly, we unlock both the pi_lock of the task, as well as the mutex's
492       we have taken that task's pi_lock at the beginning of the loop.
499       protected only by the task's pi_lock.  But the code to unlock the mutex
505       wait_lock.  If we fail that lock, we release the pi_lock of the
509       the entire time, and it is not let go when we grab the pi_lock of the
512       wait_lock, the unlocking code would spin on the new owner's pi_lock
514       fail the spin_trylock on the wait_lock, release the pi_lock, and
745 On the wake up code, the pi_lock of the current owner is taken.  The top
753 The pi_lock of the previous owner is released, and the new pending owner's
754 pi_lock is taken.  Remember that this is the trick to prevent the race
762 Finally we unlock the pi_lock of the pending owner and wake it up.