Lines Matching refs:grab

35 priority process, C is the lowest, and B is in between. A tries to grab a lock
46    grab lock L1 (owned by C)
459 pi_lock and wait_lock goes in the opposite direction. If we fail to grab the
489       since we just grab the mutex's wait_lock. And one could be right.
509       the entire time, and it is not let go when we grab the pi_lock of the
549 priority process comes in and tries to grab that mutex.  If a higher priority
579 does not implement CMPXCHG would always grab the lock (if there's no
582 try_to_take_rt_mutex is used every time the task tries to grab a mutex in the
590 slow unlock path, and it would then need to grab the wait_lock, which this
605   owner to grab the mutex.  When a pending owner wakes up, it checks to see
624   from itself.  When the pending owner tries to grab the mutex, it will fail
635   3) Failed to grab ownership
694 In any of these cases, we continue the loop and once again try to grab the