Skip to content

Latest commit

 

History

History
115 lines (79 loc) · 5.21 KB

ns-ntddndis-_ndis_sriov_vf_invalidate_config_block_info.md

File metadata and controls

115 lines (79 loc) · 5.21 KB
Raw
UID title description old-location tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NS:ntddndis._NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
_NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO (ntddndis.h)
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.
netvista\ndis_sriov_vf_invalidate_config_block_info.htm
netvista
05/02/2018
NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure
*PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO, NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO, NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure [Network Drivers Starting with Windows Vista], PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO, PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure pointer [Network Drivers Starting with Windows Vista], _NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO, netvista.ndis_sriov_vf_invalidate_config_block_info, ntddndis/NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO, ntddndis/PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
ntddndis.h
Ndis.h
Windows
Supported in NDIS 6.30 and later.
Windows
NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO, *PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
_NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
ntddndis/_NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
ntddndis/PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
ntddndis/NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
APIRef
kbSyntax
HeaderDef
Ntddndis.h
_NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
PNDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO
NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO

_NDIS_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO structure

-description

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.

-struct-fields

-field Header

The 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:

NDIS_SIZEOF_SRIOV_VF_INVALIDATE_CONFIG_BLOCK_INFO_REVISION_1

Original version for NDIS 6.30 and later.

Set the Size member to NDIS_SIZEOF_SRIOV_VF_CONFIG_STATE_REVISION_1.

-field BlockMask

A 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.

-remarks

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 VF miniport driver, which runs in the guest operating system. This operating system runs within a Hyper-V child partition.
  • 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.

-see-also

NDIS_OBJECT_HEADER

OID_SRIOV_VF_INVALIDATE_CONFIG_BLOCK