lywsvip/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2026-09-08 18:30:51 +08:00
Code Issues Packages Projects Releases Wiki Activity

[NTOS:EX] Document push lock list optimization state

Browse Source 
Rename the ExpOptimizePushLockList argument from OldValue to Initial
Value to reflect that it's the lock avlue installed by the caller when
setting Waking.

Document and assert the required Locked,Waiting, and Waking state, and
clarify that the routine either completes the waiter list links and
clears Waking or enters the wakeup if the lock has been released.
This commit is contained in:
Gleb Surikov
2026-08-04 00:07:27 +03:00
committed by Mikhail Tyukin
parent 4acacdb7e9
commit 01ec4e184f
1 changed files with 14 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
ntoskrnl/ex/pushlock.c
View File

@@ -219,21 +219,30 @@ ExfWakePushLock(PEX_PUSH_LOCK PushLock,
* @param PushLock
* Pointer to a pushlock whose waiter list needs to be optimized.
*
* @param OldValue
* Last known value of the pushlock before this routine was called.
* @param InitialValue
* Last known value of the pushlock installed by the caller when
* it inserted a new wait block and set the Waking bit.
*
* @return None.
*
* @remarks At the end of the optimization, the pushlock will also be wakened.
* @remarks If the pushlock remains locked, this routine completes
* the wait block links and clears Waking. If the lock has
* been released, the pushlock will be wakened.
*
*--*/
VOID
FASTCALL
ExpOptimizePushLockList(PEX_PUSH_LOCK PushLock,
EX_PUSH_LOCK OldValue)
EX_PUSH_LOCK InitialValue)
{
PEX_PUSH_LOCK_WAIT_BLOCK WaitBlock, LastWaitBlock, PreviousWaitBlock, FirstWaitBlock;
EX_PUSH_LOCK NewValue;
EX_PUSH_LOCK OldValue, NewValue;
ASSERT(InitialValue.Locked);
ASSERT(InitialValue.Waiting);
ASSERT(InitialValue.Waking);
OldValue = InitialValue;
/* Start main loop */
for (;;)