A kernel subsystem that manages kernel objects.
See presentation lock.
An event that occurs when a process attempts to access data or code that is not resident in memory.
A region of kernel-space memory that is not physically resident and therefore can be written to the hard drive if necessary and then read back in when needed.
A queue dispatching technique in which a queue delivers I/O requests to the driver as soon as possible, whether or not another request is already active in the driver.
The operating level at which no interrupts are masked off. This is the level at which most applications and system software run.
physical device object
A device object that represents a device for its bus driver.
An endpoint on a USB device that is configured in the current alternate setting in an interface.
A combination of system software, device hardware, and device driver support through which a computer system can recognize and adapt to hardware configuration changes with little or no intervention by an end user.
A kernel subsystem that manages Plug and Play operations.
A four-byte character literal that is associated with a dynamically allocated chunk of pool memory. A driver specifies the tag when it allocates the memory.
The PREfast state of analysis just after a function call has returned.
A queue that the framework manages in accordance with the Plug and Play and power state of the parent device object. Such a queue stops dispatching requests when the device leaves the working state and resumes dispatching requests when the device reenters the working state.
The set of rules that determine how and when a system or device changes power state.
The level of power consumption for the system or for an individual device.
The PREfast state of analysis just before a function call is made.
A framework-created lock for device and queue objects that the framework uses to implement synchronization scope.
An annotation from which more complex annotations can be constructed.
An attribute of a thread that determines when and how often the thread is scheduled to run.
A set of system-defined constant values that are used to increase the thread priority of the requesting application when drivers complete an I/O request.
To check that a memory address range is in user-mode address space and that the range can be read or written in the current process context.
An area in the registry in which a UMDF driver can store information about its device.