summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2026-07-08 12:34:35 +0200
committerPaolo Abeni <pabeni@redhat.com>2026-07-08 12:34:36 +0200
commit2f1671d45247d7973f9b51b3ed8dbdab8c3ee7f7 (patch)
treed32b1bae6daba34998d544827916224140a85216 /tools/perf/scripts/python
parentbcd2e8b40ef955038d9af137d3ebeb0de786d835 (diff)
parent47467501cb88d65f5f3b6eee1cf0b6704b6c43e1 (diff)
Merge branch 'selftests-drv-net-run-xdp-tests-with-both-ip-versions'
Nimrod Oren says: ==================== selftests: drv-net: run XDP tests with both IP versions The driver selftest environment picks a single address family for tests which use the generic address fields. When both IPv4 and IPv6 are available it prefers IPv6, which can leave IPv4 paths untested and hide IPv4-only bugs. This happened recently in the XDP selftest, where an IPv4 checksum bug was missed when IPv6 was also configured. XDP traffic handling has IP-version-specific code paths, and the follow-up discussion concluded that the XDP tests should run against both IP versions [1]. This series changes NetDrvEpEnv from exposing only the initially selected address family to allowing tests to switch the generic address fields between IP versions. xdp.py uses this to run the XDP traffic cases over both IPv4 and IPv6. Test variants whose required IP version is not configured are skipped. [1] https://lore.kernel.org/20260518143138.74839bf9@kernel.org/ ==================== Link: https://patch.msgid.link/20260702062348.2123960-1-noren@nvidia.com Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions