Lines Matching refs:blocked

80            blocked on one of its locks.  This is described in more detail
95 waiter   - A waiter is a struct that is stored on the stack of a blocked
97            a process being blocked on the mutex, it is fine to allocate
100            the task is blocked on.  It also has the plist node structures to
107 waiters  - A list of processes that are blocked on a mutex.
123 would never diverge, since a process can't be blocked on more than one
132            B blocked on L1
134                   C blocked on L2
136                          D blocked on L3
138                                 E blocked on L4
145 another mutex L5 where B owns L5 and F is blocked on mutex L5.
151 Since a process may own more than one mutex, but never be blocked on more than
166 Also since a mutex may have more than one process blocked on it, we can
168 blocked on mutex L2:
207 Every mutex keeps track of all the waiters that are blocked on itself. The mutex
220 blocked on mutexes owned by the process.
289        C blocked on L3
291               B blocked on L2
293                      A blocked on L1
392 process has just blocked on a mutex owned by the task, __rt_mutex_adjust_prio
416 that is the process's waiter struct that is blocked on the mutex (although this
429 in the pi_lists and wait_lists that the task is blocked on.  This function
438 If the task is not blocked on a mutex then the loop is exited.  We are at
441 A check is now done to see if the original waiter (the process that is blocked
444 there is another process higher in priority that is blocked on one of the
457 Next, we look at the mutex that the task is blocked on. The mutex's wait_lock
463 the mutex the task is blocked on, we update the task's waiter's plist node
497       end of the PI chain is when the task isn't blocked on anything or the
534 blocked on, when the mutex is released it would be given to the lower priority
547 new process is given a mutex that it was blocked on, it is only given
614   is never blocked on a mutex.  So there is no PI chain to worry about.  It also
617   blocked on the current mutex.
658 The waiter structure has a "task" field that points to the task that is blocked
679 If the owner is also blocked on a lock, and had its pi_list changed
683 Now all locks are released, and if the current process is still blocked on a
750 as the "Has Waiters" bit if there still are other processes blocked on the