Datasheet

37
Errata—Intel
®
82599 10 GbE Controller
Workaround:
Keep a dummy Tx queue active in a reserved, lowest priority TC, transmitting packets that are dropped
by an internal IOV related configuration (requires partial internal IOV configuration. Does NOT require
real IOV). This avoids an empty condition, which avoids the issue.
Status: B0=Yes; NoFix
35 SR-IOV: PCIe Capability Structure in VF Area Is
Incorrectly Implemented
Problem:
SR-IOV Specification 1.0 section 3.5, 3.5.2, 3.5.3, 3.5.6, and 3.5.9 requires that the virtual function's
PCIe Capability Structure inherits its basic values from its matching physical function, including Device
Capabilities, Link Capabilities and Device Capabilities 2 registers. Currently, the 82599 is returning
zeros when reading those registers, as well as the PCIe version field.
Implication:
SR-IOV might be unsupported by VMM, or by VF drivers. There is no implication for Microsoft* and
VMware ESX* SR-IOV solutions.
Workaround:
VMM needs to be aware of this issue, and return relevant PF capability registers.
Status: B0=Yes; NoFix
36 SR-IOV: Incorrect Completer ID for Config-Space
Transactions
Problem:
According to PCIe Spec 2.0 clause 2.2.9, the PCIe hardware must include a Completer-ID field in all
completions for incoming NP requests, using the address specified in each incoming Type 0 CfgWr
transaction. However, the 82599 replies for incoming SR-IOV configuration transactions (CfgRd/CfgWr)
with a false Completer-ID having a wrong function ID, which violates the PCIe specification.
Implication:
Software should be able to operate successfully without any impact. Although the specification requires
sending completions with Completer-ID, comparing it upstream is implicit. This is because the PCIe
Transaction-ID includes the Requester-ID and the Transaction Tag (and does not relate the Completer-
ID). Furthermore, responses to Config Accesses are always Dword size, and their completions arrive in
order.
Workaround:
Ignore the Completer-ID where referred.
Status: B0=Yes; NoFix