PEP_SOC_SUBSYSTEM_METADATA - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// pep_x.h
typedef struct _PEP_SOC_SUBSYSTEM_METADATA {
[in/out] UNICODE_STRING Key;
[in/out] UNICODE_STRING Value;
} PEP_SOC_SUBSYSTEM_METADATA, *PPEP_SOC_SUBSYSTEM_METADATA;
View the official Windows Driver Kit DDI reference// pepfx.h
typedef struct _PEP_SOC_SUBSYSTEM_METADATA {
[in/out] UNICODE_STRING Key;
[in/out] UNICODE_STRING Value;
} PEP_SOC_SUBSYSTEM_METADATA, *PPEP_SOC_SUBSYSTEM_METADATA;
View the official Windows Driver Kit DDI referenceNo description available.
The PEP_SOC_SUBSYSTEM_METADATA structure contains key-value pairs that contain metadata for a system on a chip (SoC) subsystem. It is used in the context of a PEP_DPM_QUERY_SOC_SUBSYSTEM_METADATA notification sent to a platform extension plug-in (PEP).
Key [in/out]A buffer for the PEP to write the key portion of the metadata string-pair. Key must be unique among all Key values reported by this subsystem.
Prior to entry into the notification callback routine, the kernel will:
Prior to exit from the callback routine, the PEP must copy a null-terminated string into Key.Buffer and update Key.Length with a byte count that is sizeof(WCHAR) times the number of UNICODE characters copied, not including the terminating UNICODE_NULL.
The PEP must use the allocated memory that is pointed to by the address in Key.Buffer to provide the key. Since this memory is pre-allocated, its size cannot be changed. The PEP is responsible for truncating the key string, if necessary, so that it does not exceed the length specified in Key.MaximumLength (including the terminating UNICODE_NULL character).
Value [in/out]A buffer for the PEP to write the value portion of the metadata string-pair.
Prior to entry into the notification callback routine, the kernel will:
Prior to exit from the callback routine, the PEP must copy a null-terminated string into Value.Buffer and update Value.Length with a byte count that is sizeof(WCHAR) times the number of UNICODE characters copied, not including the terminating UNICODE_NULL.
The PEP must use the allocated memory that is pointed to by the address in Value.Buffer to provide the metadata value. Since this memory is pre-allocated, its size cannot be changed. The PEP is responsible for truncating the value string, if necessary, so that it does not exceed the length specified in Value.MaximumLength (including the terminating UNICODE_NULL character).
PEP_DPM_QUERY_SOC_SUBSYSTEM_METADATA
PEP_QUERY_SOC_SUBSYSTEM_METADATA
The PEP_SOC_SUBSYSTEM_METADATA structure contains key-value pairs that contain metadata for a system on a chip (SoC) subsystem. It is used in the context of a PEP_DPM_QUERY_SOC_SUBSYSTEM_METADATA notification sent to a platform extension plug-in (PEP).
Key [in/out]A buffer for the PEP to write the key portion of the metadata string-pair. Key must be unique among all Key values reported by this subsystem.
Prior to entry into the notification callback routine, the kernel will:
Prior to exit from the callback routine, the PEP must copy a null-terminated string into Key.Buffer and update Key.Length with a byte count that is sizeof(WCHAR) times the number of UNICODE characters copied, not including the terminating UNICODE_NULL.
The PEP must use the allocated memory that is pointed to by the address in Key.Buffer to provide the key. Since this memory is pre-allocated, its size cannot be changed. The PEP is responsible for truncating the key string, if necessary, so that it does not exceed the length specified in Key.MaximumLength (including the terminating UNICODE_NULL character).
Value [in/out]A buffer for the PEP to write the value portion of the metadata string-pair.
Prior to entry into the notification callback routine, the kernel will:
Prior to exit from the callback routine, the PEP must copy a null-terminated string into Value.Buffer and update Value.Length with a byte count that is sizeof(WCHAR) times the number of UNICODE characters copied, not including the terminating UNICODE_NULL.
The PEP must use the allocated memory that is pointed to by the address in Value.Buffer to provide the metadata value. Since this memory is pre-allocated, its size cannot be changed. The PEP is responsible for truncating the value string, if necessary, so that it does not exceed the length specified in Value.MaximumLength (including the terminating UNICODE_NULL character).
PEP_DPM_QUERY_SOC_SUBSYSTEM_METADATA
PEP_QUERY_SOC_SUBSYSTEM_METADATA