Lines Matching full:mutex
30 A mutex holds a volatile 32-bit recursion count, and a volatile 32-bit
31 identifier denoting its owner. A mutex is considered signaled when its
36 A mutex also holds an internal flag denoting whether its previous owner
37 has died; such a mutex is said to be abandoned. Owner death is not
39 communicated using ``NTSYNC_IOC_MUTEX_KILL``. An abandoned mutex is
123 Create a mutex object. Takes a pointer to struct
129 - Initial recursion count of the mutex.
131 - Initial owner of the mutex.
135 On success, returns a file descriptor the created mutex.
170 Release a mutex object. Takes a pointer to struct
176 - Specifies the owner trying to release this mutex.
181 is not the current owner of the mutex, the ioctl fails with
184 The mutex's count will be decremented by one. If decrementing the
185 mutex's count causes it to become zero, the mutex is marked as
230 Read the current state of a mutex object. Takes a pointer to struct
236 - On output, contains the current owner of the mutex, or zero
237 if the mutex is not currently owned.
239 - On output, contains the current recursion count of the mutex.
241 If the mutex is marked as abandoned, the function fails with
260 Mark a mutex as unowned and abandoned if it is owned by the given
263 owner does not own the mutex, the function fails with ``EPERM``.
265 Eligible threads waiting on the mutex will be woken as appropriate
294 - Mutex owner identifier. If any object in ``objs`` is a mutex,
295 the ioctl will attempt to acquire that mutex on behalf of
321 is acquired by decrementing its count by one. A mutex is considered
330 ``owner`` identifiers) are queued on the same mutex, only one is
334 If an abandoned mutex is acquired, the ioctl fails with
336 otherwise be considered successful. The mutex is marked as owned by
338 abandoned, and ``index`` is still set to the index of the mutex.
369 If an abandoned mutex is acquired, the ioctl fails with
371 nevertheless marked as acquired. Note that if multiple mutex objects