READ_WRITE_MITIGATED_REGISTER callback function (pcivirt.h)
Reads or writes to mitigated address spaces.
Syntax
READ_WRITE_MITIGATED_REGISTER ReadWriteMitigatedRegister;
NTSTATUS ReadWriteMitigatedRegister(
[in] PVOID Context,
[in] USHORT VfIndex,
[in] BOOLEAN Read,
[in] USHORT BarIndex,
[in] ULONGLONG Offset,
[in] ULONG Length,
[in, out] PUCHAR Data
)
{...}
Parameters
[in] Context
A pointer to a driver-defined context.
[in] VfIndex
A zero-based index of the VF to which this read/write operation applies.
[in] Read
A boolean that indicates whether to perform a read or a write operation. TRUE indicates read, FALSE otherwise.
[in] BarIndex
The BAR that maps the address space being mitigated.
[in] Offset
The offset in number of bytes into the BAR at which this access begins.
[in] Length
The length in bytes of this read or write operation.
[in, out] Data
A pointer to a buffer that contains the data to read or write.
Return value
Return STATUS_SUCCESS if the operation succeeds. Otherwise, return an appropriate NTSTATUS error code.
Remarks
This callback function is implemented by the physical function (PF) driver. It is invoked when the system wants to read or write from a mitigable register.
The PF driver registers its implementation by setting the ReadWriteMitigatedRegister member of the MITIGABLE_DEVICE_INTERFACE, configuring a WDF_QUERY_INTERFACE_CONFIG structure, and calling WdfDeviceAddQueryInterface.
Requirements
Requirement | Value |
---|---|
Minimum supported client | Windows 10 |
Minimum supported server | Windows Server 2016 |
Target Platform | Windows |
Header | pcivirt.h |
IRQL | PASSIVE_LEVEL |
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for