PEP_WORK_POWER_CONTROL - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// pep_x.h
typedef struct _PEP_WORK_POWER_CONTROL {
POHANDLE DeviceHandle;
[in] LPCGUID PowerControlCode;
PVOID RequestContext;
[in] PVOID InBuffer;
[in] SIZE_T InBufferSize;
[in] PVOID OutBuffer;
[in] SIZE_T OutBufferSize;
} PEP_WORK_POWER_CONTROL, *PPEP_WORK_POWER_CONTROL;
View the official Windows Driver Kit DDI reference// pepfx.h
typedef struct _PEP_WORK_POWER_CONTROL {
POHANDLE DeviceHandle;
[in] LPCGUID PowerControlCode;
PVOID RequestContext;
[in] PVOID InBuffer;
[in] SIZE_T InBufferSize;
[in] PVOID OutBuffer;
[in] SIZE_T OutBufferSize;
} PEP_WORK_POWER_CONTROL, *PPEP_WORK_POWER_CONTROL;
View the official Windows Driver Kit DDI referenceNo description available.
The PEP_WORK_POWER_CONTROL structure contains the parameters for a power control request that the platform extension plug-in (PEP) sends directly to a processor driver.
DeviceHandleA POHANDLE value that identifies the processor. The PEP received this handle in a previous PEP_DPM_REGISTER_DEVICE notification.
PowerControlCode [in]A pointer to a GUID value that specifies the power control operation to perform.
RequestContextA pointer to a PEP-defined context value. The PEP might use this value to uniquely identify a power control request message (in case the PEP issues multiple requests with the same control code to the same device).
InBuffer [in]A pointer to a driver-allocated input buffer that contains the input parameters for this power control operation.
InBufferSize [in]The size in bytes of the buffer pointed to by InBuffer.
OutBuffer [in]A pointer to a driver-allocated output buffer to which the PEP writes the results of this power control operation.
OutBufferSize [in]The size in bytes of the buffer pointed to by OutBuffer.
The PowerControl member of the PEP_WORK_INFORMATION structure is a pointer to a PEP_WORK_POWER_CONTROL structure.
The PEP issues a power control request from a worker thread. The Windows power management framework (PoFx) forwards this request by calling the processor driver's PowerControlCallback routine, if the driver implements this routine.
GUID
The PEP_WORK_POWER_CONTROL structure contains the parameters for a power control request that the platform extension plug-in (PEP) sends directly to a processor driver.
DeviceHandleA POHANDLE value that identifies the processor. The PEP received this handle in a previous PEP_DPM_REGISTER_DEVICE notification.
PowerControlCode [in]A pointer to a GUID value that specifies the power control operation to perform.
RequestContextA pointer to a PEP-defined context value. The PEP might use this value to uniquely identify a power control request message (in case the PEP issues multiple requests with the same control code to the same device).
InBuffer [in]A pointer to a driver-allocated input buffer that contains the input parameters for this power control operation.
InBufferSize [in]The size in bytes of the buffer pointed to by InBuffer.
OutBuffer [in]A pointer to a driver-allocated output buffer to which the PEP writes the results of this power control operation.
OutBufferSize [in]The size in bytes of the buffer pointed to by OutBuffer.
The PowerControl member of the PEP_WORK_INFORMATION structure is a pointer to a PEP_WORK_POWER_CONTROL structure.
The PEP issues a power control request from a worker thread. The Windows power management framework (PoFx) forwards this request by calling the processor driver's PowerControlCallback routine, if the driver implements this routine.
GUID