src/sys/dev/iavf, branch release/14.4.0

pci: Don't cache the count of MSI/MSI-X messages before allocation

2025-04-29T14:24:32Z

A device can in theory change the read-only fields in the MSI/MSI-X control registers that indicate the maximum number of supported registers in response to changing other device registers. For example, certain Intel networking VFs change the number of messages as a result of changes in the PCI_IOV_ADD_VF callback. To support this, always read the current value of the relevant control register in the *_count and *_alloc methods. Once messages have been allocated, the control register value remains cached. Reported by: Krzysztof Galazka Reviewed by: Krzysztof Galazka , erj Differential Revision: https://reviews.freebsd.org/D48890 (cherry picked from commit 346020138a0fd20085ebc285f090df38d7d18527)

iavf(4): Get MSI-X BAR index at runtime instead of hardcoding it

2024-10-31T16:54:24Z

This allows iavf to load on E830 devices since those devices place their MSI-X BAR at a different location than in previous 800 series products. Signed-off-by: Eric Joyner Sponsored by: Intel Corporation Differential Revision: https://reviews.freebsd.org/D46952 (cherry picked from commit e53a21abdf2953714e44e3c54b4bb78557cb096c)

Fix enum warning in iavf

2024-08-04T10:21:33Z

This fixes a clang 19 warning: sys/dev/iavf/iavf_lib.c:514:39: error: comparison of different enumeration types ('enum virtchnl_vsi_type' and 'enum iavf_vsi_type') [-Werror,-Wenum-compare] 514 | if (sc->vf_res->vsi_res[i].vsi_type == IAVF_VSI_SRIOV) | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~~~~~~~~~~~ The `vsi_type` field of `struct virtchnl_vsi_resource` is of type `enum virtchnl_vsi_type`, not `enum iavf_vsi_type`. In this case, we can seamlessly replace the value with `VIRTCHNL_VSI_SRIOV`, which is numerically equal to `IAVF_VSI_SRIOV`. MFC after: 3 days (cherry picked from commit 67be1e195acfaec99ce4fffeb17111ce085755f7)

iavf: Add explicit ifdi_needs_reset for VLAN changes

2023-08-24T20:46:56Z

In rS360398, a new iflib device method was added with default of opt out for VLAN events needing an interface reset. iavf(4) was the original need for this, because VLAN filter changes currently have negative interactions with Malicious Driver Detection. Add iavf_if_needs_restart and explicitly enable VLAN re-init. MFC after: 2 weeks Sponsored by: BBOX.io Differential Revision: https://reviews.freebsd.org/D41558

iavf: remove compatibility code and address some warnings

2023-08-23T12:48:11Z

Code for pre-11 FreeBSD versions is removed. Also removed are macros that are not used anymore and "i" variable does not shadow anymore other "i" variable. Differential Revision: https://reviews.freebsd.org/D41547 Approved by: erj

iflib drivers: Constify PCI ID LUTs

2023-08-17T18:34:23Z

Since d49e83eac3baf16a22b1c5d42e8438b68b17e6f9, iflib(9) is ready for this change. While at it, make isc_driver_version strings (static) const where not apparently un-const on purpose, too. This reduces the size of the amd64 GENERIC by about 10 KiB.

sys: Remove $FreeBSD$: one-line .c comment pattern

2023-08-16T17:54:24Z

Remove /^/[*/]\s*\$FreeBSD\$.*\n/

iavf: purge EOL release compatibility

2023-02-04T16:13:08Z

Drop code that differentiated between FreeBSD 10 and 11 Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/603 Differential Revision: https://reviews.freebsd.org/D35560

Mechanically convert iavf(4) to IfAPI

2023-01-24T19:36:29Z

Reviewed by: erj Sponsored by: Juniper Networks, Inc. Differential Revision: https://reviews.freebsd.org/D37858

iavf/ice/ixl: Remove unused devclass arguments to DRIVER_MODULE.

2022-05-06T22:46:59Z