Page MenuHomeFreeBSD

ixv: Add Hyper-V virtual function support
Needs ReviewPublic

Authored by kbowling on Mon, Sep 7, 4:11 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Sep 7, 5:10 AM
Unknown Object (File)
Mon, Sep 7, 5:10 AM
Unknown Object (File)
Mon, Sep 7, 5:08 AM
Subscribers

Details

Reviewers
whu
kgalazka
Group Reviewers
Intel Networking
Restricted Owners Package(Owns No Changed Paths)
Summary
Hyper-V does not expose the normal Intel PF/VF mailbox.

Import the Hyper-V operation overrides from DPDK and complete its reset
callback with the configuration-space mechanism submitted by Microsoft.
Route ixv operations through the operation table, use mailbox API 1.0,
and limit this environment to one queue pair.

Claim the 82599, X540, X550, X550EM-X, and X550EM-A Hyper-V device IDs
listed by DPDK.  Select the same path for the E610 Hyper-V subdevice
identity defined there.

For E610/Linkville, read the emulated VFLINKS-format status from PCI
configuration space at offset 0x209.  Older families retain the MMIO
VFLINKS path.

Treat receive-mode changes as host-owned no-ops and do not retry VLAN
operations that Hyper-V permanently rejects.  Limit the Hyper-V 82599
MTU to 1504 because its VF does not implement the X540 RLPML field.

Use mailbox reset indications only to refresh cached Hyper-V link state.
Hyper-V does not provide the mailbox handshake required to treat that
indication as a request for an iflib reinitialization.

PR:             232472, 239849
Obtained from:  DPDK
Sponsored by:   BBOX.io
Co-authored-by: Wei Hu <weh@microsoft.com>

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped