Lines Matching refs:kernel

7 futexes, for kernel assist of cleanup of held locks on task exit.
11 are taken and dropped, without kernel intervention.  The only additional
12 kernel intervention required for robust_futexes above and beyond what is
15  1) a one time call, per thread, to tell the kernel where its list of
17  2) internal kernel code at exit, to handle any listed locks held
23 threads in the kernel.  Options on the sys_futex(2) system call support
29 necessary list elements exactly as the kernel expects them.  If it fails
46 kernel, then it can actually have two such structures - one using 32 bit
48 bit native mode.  The kernel, if it is a 64 bit kernel supporting 32 bit
79 robust_futexes.  The kernel will only be able to wakeup the next thread
81 mechanism to register the address of that 'lock word' with the kernel.
87 the kernel will walk this list, mark any such locks with a bit
92 anticipates using robust_futexes, the kernel stores the passed in 'head'
101 larger, user level locking structures, one per lock.  The kernel
107 linked list, but that doesn't matter to the kernel.
110 pointer known to the kernel, the kernel can provide to a thread the
132 the kernel to correctly handle lock cleanup regardless of when the task
152 On exit, the kernel will consider the address stored in
156 exiting threads TID, then the kernel will do two things:
164 they were waiting, and bit 30 is set by the kernel to indicate that the
167 The kernel exit code will silently stop scanning the list further if at
176     future kernel configuration changes) elements.
178 When the kernel sees a list entry whose 'lock word' doesn't have the