Skip to content

Latest commit

 

History

History
77 lines (56 loc) · 2.45 KB

nf-wdm-kestallexecutionprocessor.md

File metadata and controls

77 lines (56 loc) · 2.45 KB
UID title description old-location tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NF:wdm.KeStallExecutionProcessor
KeStallExecutionProcessor function (wdm.h)
The KeStallExecutionProcessor routine in wdm.h stalls the caller on the current processor for a specified time interval.
kernel\kestallexecutionprocessor.htm
kernel
04/30/2018
KeStallExecutionProcessor function
KeStallExecutionProcessor, KeStallExecutionProcessor routine [Kernel-Mode Driver Architecture], k105_47405815-7368-4100-b39d-43f5a242f5c1.xml, kernel.kestallexecutionprocessor, wdm/KeStallExecutionProcessor
wdm.h
Wdm.h, Ntddk.h, Ntifs.h
Universal
Available starting with Windows 2000.
Hal.lib
Hal.dll
Any level
Windows
KeStallExecutionProcessor
wdm/KeStallExecutionProcessor
APIRef
kbSyntax
DllExport
Hal.dll
KeStallExecutionProcessor

KeStallExecutionProcessor function (wdm.h)

-description

The KeStallExecutionProcessor routine stalls the caller on the current processor for a specified time interval.

-parameters

-param MicroSeconds [in]

Specifies the number of microseconds to stall.

-returns

None

-remarks

KeStallExecutionProcessor is a processor-dependent routine that busy-waits for at least the specified number of microseconds, but not significantly longer.

This routine is for use by device drivers and other software that must wait for an interval of less than a clock tick but more than for a few instructions. If you use this routine you must minimize the stall interval, typically to less than 50 microseconds. If a driver must wait for a longer interval, you should use a different synchronization technique.

-see-also

KeDelayExecutionThread

KeWaitForMultipleObjects

KeWaitForSingleObject