summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-08-10 17:46:45 -0700
committerJakub Kicinski <kuba@kernel.org>2026-08-11 18:31:19 -0700
commit878b56de01e255172745775cd8afcec2bd80268a (patch)
tree8e465f2fe07ee186af0aad14f52954119b4bdc34 /tools/perf/scripts/python/bin/stackcollapse-record
parent5838193edccab7810d5dc51c165a316089272dc6 (diff)
selftests: drv-net: hide the devlink port_split test
The devlink port_split test has limited applicability. NICs (as opposed to switches) require at least a re-probe to apply the split configuration. On top of that the test is not compatible with our driver env, it just splits all ports on the system, not only what NETIF points at. Long term we may want to add some indication in devlink whether the port splitting is runtime (cmode of sorts), and fix the test to follow driver env. But since no (known) NIC driver can support runtime anyway let's just hide the test from the selftest framework by moving it to extra files. Having this test randomly break unrelated NICs within the DUT makes people implement allow-lists for ksft, which then means their setups don't run new tests. It's very useful during test review to see whether the test works across all the runners. Reviewed-by: Petr Machata <petrm@nvidia.com> Link: https://patch.msgid.link/20260811004645.1072124-1-kuba@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions