NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ntddndis.h
typedef struct _NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO {
NDIS_OBJECT_HEADER Header;
ULONG64 BlockMask;
} NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO, *PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO;
View the official Windows Driver Kit DDI referenceNo description available.
The NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure specifies one or more Virtual Function (VF) configuration blocks whose data has been changed (invalidated) by the driver for the PCI Express (PCIe) Physical Function (PF) on the network adapter.
HeaderThe type, revision, and size of the NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure. This member is formatted as an NDIS_OBJECT_HEADER structure.
The miniport driver must set the Type member of Header to NDIS_OBJECT_TYPE_DEFAULT. To specify the version of the NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure, the miniport driver must set the Revision member of Header to the following value:
Original version for NDIS 6.30 and later.
Set the Size member to NDIS_SIZEOF_SRIOV_VF_CONFIG_STATE_REVISION_1.
BlockMaskA ULONG64 value that specifies a bitmask for the first 64 VF configuration blocks. Each bit in the bitmask corresponds to a VF configuration block. If the bit is set to one, the data associated with the corresponding VF configuration block has changed.
The NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure is used in OID set requests of OID_SRIOV_VF_INVALIDATE_CONFIG_BLOCK.
A VF configuration block is used for backchannel communication between the drivers of the PCIe PF and a VF on a device that supports the SR-IOV interface. Data from a VF configuration block can be exchanged between the following drivers:
The PF miniport driver, which runs in the management operating system.
This operating system runs within the Hyper-V parent partition.
Note The usage of the VF configuration block and the format of its configuration data are defined by the independent hardware vendor (IHV) of the device. The configuration data is used only by the PF and VF miniport drivers.
However, we recommend that IHVs reserve the first 64 VF configuration blocks for data that may change occasionally.
For more information about backchannel communication within the single root I/O virtualization (SR-IOV) interface, see SR-IOV PF/VF Backchannel Communication.
OID_SRIOV_VF_INVALIDATE_CONFIG_BLOCK