b76fafb174
The incriminated commit broke the use of RTE_PCI_DRV_IOVA_AS_VA which
was intended to mean "driver only supports VA" but had been understood
as "driver supports both PA and VA" by most net drivers and used to let
dpdk processes to run as non root (which do not have access to physical
addresses on recent kernels).
The check on physical addresses actually closed the gap for those
drivers. We don't need to mark them with RTE_PCI_DRV_IOVA_AS_VA and this
flag can retain its intended meaning.
Document explicitly its meaning.
We can check that a driver requirement wrt to IOVA mode is fulfilled
before trying to probe a device.
Finally, document the heuristic used to select the IOVA mode and hope
that we won't break it again.
Fixes:
|
||
|---|---|---|
| .. | ||
| base | ||
| iavf_ethdev.c | ||
| iavf_log.h | ||
| iavf_rxtx_vec_common.h | ||
| iavf_rxtx_vec_sse.c | ||
| iavf_rxtx.c | ||
| iavf_rxtx.h | ||
| iavf_vchnl.c | ||
| iavf.h | ||
| Makefile | ||
| meson.build | ||
| rte_pmd_iavf_version.map | ||