The KeReleaseMutex routine releases a mutex object, and specifies whether the caller is to call one of the KeWaitXxx routines as soon as KeReleaseMutex returns control.
- Mutex [in, out]
A pointer to an initialized mutex object for which the caller provides the storage.
- Wait [in]
Specifies whether the call to KeReleaseMutex is to be immediately followed by a call to one of the KeWaitXxx routines. If TRUE, the KeReleaseMutex call must be followed by a call to KeWaitForMultipleObjects, KeWaitForMutexObject, or KeWaitForSingleObject. For more information, see the following Remarks section.
If the return value is zero, the mutex object was released and attained a state of signaled.
For better performance, use fast mutexes or guarded mutexes. For more information, see Alternatives to Mutex Objects.
If the mutex object attains a signaled state, an attempt is made to satisfy a wait for the mutex object.
A mutex object can be released only by the thread that currently holds the mutex. If an attempt is made to release a mutex that the thread does not hold, the routine raises a STATUS_ABANDONED or STATUS_MUTEX_NOT_OWNED exception.
When a mutex object attains a signaled state, it is removed from the list of the mutexes that are held by that thread. If this list contains no more entries, the original priority for the thread is restored.
The KeReleaseMutex routine might temporarily raise the IRQL. If the Wait parameter is FALSE, the routine, before it returns, restores the IRQL to the original value that it had at the start of the call.
If Wait = TRUE, the routine returns without lowering the IRQL. In this case, the KeReleaseMutex call must be immediately followed by a KeWaitXxx call. By setting Wait = TRUE, the caller can prevent an unnecessary context switch from occurring between the KeReleaseMutex call and the KeWaitXxx call. The KeWaitXxx routine, before it returns, restores the IRQL to its original value at the start of the KeReleaseMutex call. Although the IRQL disables context switches between the two calls, these calls cannot reliably be used as the start and end of an atomic operation. For example, between these two calls, a thread that is running at the same time on another processor might change the state of the event object or of the target of the wait.
If the caller is executing at IRQL = DISPATCH_LEVEL or in an arbitrary thread context, the Timeout parameter to KeWaitXxx must be zero.
If a mutex is acquired recursively, the holding thread must call KeReleaseMutex as many times as it acquired the mutex to set it to the signaled state.
For more information about mutex objects, see Mutex Objects.
|Available starting with Windows 2000.|
DDI compliance rules
Build date: 2/11/2014