PEP_WORK_COMPLETE_PERF_STATE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// pep_x.h
typedef struct _PEP_WORK_COMPLETE_PERF_STATE {
POHANDLE DeviceHandle;
[in] ULONG Component;
BOOLEAN Succeeded;
} PEP_WORK_COMPLETE_PERF_STATE, *PPEP_WORK_COMPLETE_PERF_STATE;
View the official Windows Driver Kit DDI reference// pepfx.h
typedef struct _PEP_WORK_COMPLETE_PERF_STATE {
POHANDLE DeviceHandle;
[in] ULONG Component;
BOOLEAN Succeeded;
} PEP_WORK_COMPLETE_PERF_STATE, *PPEP_WORK_COMPLETE_PERF_STATE;
View the official Windows Driver Kit DDI referenceNo description available.
The PEP_WORK_COMPLETE_PERF_STATE structure describes the completion status of a previously requested update to the performance values assigned to a list of performance state (P-state) sets.
DeviceHandleA handle that represents the registration of the device with the Windows power management framework (PoFx). The PEP received this handle in a previous PEP_DPM_REGISTER_DEVICE notification.
Component [in]The index that identifies the component. This member is an index into the Components array in the PEP_DEVICE_REGISTER_V2 structure that the PEP previously supplied in response to the PEP_DPM_REGISTER_DEVICE notification for this device. If the Components array contains N elements, component indexes range from 0 to N–1.
SucceededWhether the requested P-state changes successfully completed. Set to TRUE if the PEP successfully completed all P-state changes requested in a previous PEP_DPM_REQUEST_COMPONENT_PERF_STATE notification. Set to FALSE if the PEP was unable to perform all the requested P-state changes, in which case the P-states in the hardware were left unchanged.
The CompletePerfState member of the PEP_WORK_INFORMATION structure is a PEP_WORK_COMPLETE_PERF_STATE structure. If PoFx sends a PEP_DPM_REQUEST_COMPONENT_PERF_STATE notification to request performance level changes to one or more P-state sets, and the PEP chooses to handle this request asynchronously, the PEP uses a PEP_WORK_COMPLETE_PERF_STATE structure to describe the completion status of the request.
PEP_DPM_REQUEST_COMPONENT_PERF_STATE
The PEP_WORK_COMPLETE_PERF_STATE structure describes the completion status of a previously requested update to the performance values assigned to a list of performance state (P-state) sets.
DeviceHandleA handle that represents the registration of the device with the Windows power management framework (PoFx). The PEP received this handle in a previous PEP_DPM_REGISTER_DEVICE notification.
Component [in]The index that identifies the component. This member is an index into the Components array in the PEP_DEVICE_REGISTER_V2 structure that the PEP previously supplied in response to the PEP_DPM_REGISTER_DEVICE notification for this device. If the Components array contains N elements, component indexes range from 0 to N–1.
SucceededWhether the requested P-state changes successfully completed. Set to TRUE if the PEP successfully completed all P-state changes requested in a previous PEP_DPM_REQUEST_COMPONENT_PERF_STATE notification. Set to FALSE if the PEP was unable to perform all the requested P-state changes, in which case the P-states in the hardware were left unchanged.
The CompletePerfState member of the PEP_WORK_INFORMATION structure is a PEP_WORK_COMPLETE_PERF_STATE structure. If PoFx sends a PEP_DPM_REQUEST_COMPONENT_PERF_STATE notification to request performance level changes to one or more P-state sets, and the PEP chooses to handle this request asynchronously, the PEP uses a PEP_WORK_COMPLETE_PERF_STATE structure to describe the completion status of the request.
PEP_DPM_REQUEST_COMPONENT_PERF_STATE