diff options
| author | Kevin Bowling <kbowling@FreeBSD.org> | 2026-08-10 03:38:40 +0000 |
|---|---|---|
| committer | Kevin Bowling <kbowling@FreeBSD.org> | 2026-08-10 09:55:53 +0000 |
| commit | 983e628a0c47afb47d201ce629e9619fb751254d (patch) | |
| tree | e8e0b45d048ab80300451f7f8cb6bb433d3feef0 /sys/netinet6 | |
| parent | e2daa5c06c2febacf141f9fd3a6a18cf86df8fe1 (diff) | |
ixl: Rebuild VF resources after a PF reset
A PF or EMP reset destroys the firmware switch topology, including
every VF VSI. The driver rebuilt only its PF VSI and left configured
VFs with stale switch element and VSI identifiers.
Notify VFs before a driver initiated reset, recreate the IOV VEB, and
rebuild each configured VF VSI and queue mapping after the PF switch
is restored. Keep a VF out of VFACTIVE if its reconstruction fails
so one failure cannot expose incomplete resources or prevent the PF
and other VFs from recovering.
Invalidate cached VF firmware identifiers and runtime state before
recreating the VEB. If VEB creation itself fails, teardown and mailbox
paths can no longer use pre-reset SEIDs or VSI data.
Factor the common VEB setup out of IOV initialization so initial
setup and post-reset reconstruction use the same topology and filter
sequence.
MFC after: 2 weeks
Diffstat (limited to 'sys/netinet6')
0 files changed, 0 insertions, 0 deletions
