Lines Matching refs:taken

211 interrupt context, the wait_lock can be taken without disabling interrupts.
229 called pi_lock.  This lock may also be taken in interrupt context, so when
367 to already be taken), rt_mutex_getprio, and rt_mutex_setprio.
434 taken to prevent any more changes to the pi_list of the task.  This also
458 is taken.  This is done by a spin_trylock, because the locking order of the
468 Next the owner of the mutex has its pi_lock taken, so we can update the
492       we have taken that task's pi_lock at the beginning of the loop.
501       the protection of the mutex's wait_lock, which was not taken yet.
564 taken with the CMPXCHG and nothing else needs to be done.
575 The wait_lock of the mutex is taken since the slow path of unlocking the
671 Since the wait_lock was taken at the entry of the slow lock, we can safely
709 NULL and the task needs to be taken off the wait_list of the mutex and perhaps
726 the slow unlock path is taken.
745 On the wake up code, the pi_lock of the current owner is taken.  The top
754 pi_lock is taken.  Remember that this is the trick to prevent the race