NdisMReadConfigBlock - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ndis.h
NDIS_STATUS NdisMReadConfigBlock(
[in] NDIS_HANDLE NdisMiniportHandle,
[in] ULONG BlockId,
[out] PVOID Buffer,
[in] ULONG Length
);
View the official Windows Driver Kit DDI referenceNo description available.
A miniport driver for a PCI Express (PCIe) Virtual Function (VF) calls the NdisMReadConfigBlock function to read data from a VF configuration block. Read operations for a VF configuration block are handled by the miniport driver of the network adapter's PCIe Physical Function (PF).
Note NdisMReadConfigBlock must only be called by the VF miniport driver.
NdisMiniportHandle [in]The network adapter handle that NDIS passed to the MiniportAdapterHandle parameter of MiniportInitializeEx.
BlockId [in]A ULONG value that specifies the identifier of the VF configuration block to be read. This identifier is proprietary to the independent hardware vendor (IHV) and is used only by the PF and VF miniport drivers.
Buffer [out]A pointer to a caller-allocated buffer that will contain the requested configuration data.
Length [in]The number of bytes to be read from the VF configuration block.
NdisMReadConfigBlock can return one of the following status values:
| Return code | Description |
|---|---|
| NDIS_STATUS_SUCCESS | The query operation completed successfully. |
| NDIS_STATUS_FAILURE | The query operation failed. |
The VF miniport driver calls NdisMReadConfigBlock to initiate a backchannel read request of VF configuration data by the PF miniport driver. Once notified of this request, the PF driver returns the data from the specified VF configuration block.
A VF configuration block is used for backchannel communication between the PF and VF miniport drivers. The IHV can define one or more VF configuration blocks for the device. Each VF configuration block has an IHV-defined format, length, and block ID.
Note Data from each VF configuration block is used only by the PF and VF miniport drivers.
For more information about backchannel communication within the single root I/O virtualization (SR-IOV) interface, see SR-IOV PF/VF Backchannel Communication.
For more information about the SR-IOV interface, see Overview of Single Root I/O Virtualization (SR-IOV).
If an independent hardware vendor (IHV) provides a virtual bus driver (VBD) as part of its SR-IOV driver package, its miniport driver must not call NdisMReadConfigBlock. Instead, the driver must interface with the VBD through a private communication channel, and request that the VBD call ReadVfConfigBlock. This function is exposed from the GUID_VPCI_INTERFACE_STANDARD interface that is supported by the underlying virtual PCI (VPCI) bus driver.
The VBD that runs in a Hyper-V child partition's guest operating system can query the GUID_VPCI_INTERFACE_STANDARD interface by issuing an IRP_MN_QUERY_INTERFACE request to its physical device object (PDO) on the VPCI bus. This request must be made from IRQL = PASSIVE_LEVEL. In this request, the driver must set the InterfaceType parameter to GUID_VPCI_INTERFACE_STANDARD.