Lines Matching refs:that

6 Robust_futexes provide a mechanism that is used in addition to normal
34 A thread that anticipates possibly using robust_futexes should first
51 setup that list.
60   be called the 'lock word', from that 'lock entry'.  The 'lock word'
80 waiting for a lock on a threads exit if that next thread used the futex
81 mechanism to register the address of that 'lock word' with the kernel.
84 robust_futex support for exit cleanup of that lock, it should have one
89 that lock using the futex mechanism.
93 pointer for that task.  The task may retrieve that value later on by
100 It is anticipated that threads will use robust_futexes embedded in
102 robust_futex mechanism doesn't care what else is in that structure, so
104 robust_futexes used by that thread.  The thread should link those locks
107 linked list, but that doesn't matter to the kernel.
123 lock structures for locks currently held by that thread should be on
124 that thread's robust_futex linked lock list a given time.
127 at different times by any of the threads with access to that region. The
155 bits of the 'lock word' at offset 'offset' from that address equals the
158  1) if bit 31 (0x80000000) is set in that word, then attempt a futex
159     wakeup on that address, which will waken the next thread that has
160     used to the futex mechanism to wait on that address, and
163 In the above, bit 31 was set by futex waiters on that lock to indicate
164 they were waiting, and bit 30 is set by the kernel to indicate that the
179 current threads TID in the lower 29 bits, it does nothing with that