summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2025-02-07 01:56:36 +0300
committerJakub Kicinski <kuba@kernel.org>2025-02-08 04:21:02 +0300
commit3e7efc3f4f03bca0ea630c302e7c79cf807476bb (patch)
tree2edc81d1789e4d721d4caedfc09e09c748747b52 /tools/perf/scripts/python/stackcollapse.py
parent1eb824d69f8d88405e4e80c568e8f07080309fb0 (diff)
downloadlinux-3e7efc3f4f03bca0ea630c302e7c79cf807476bb.tar.xz
net: devmem: don't call queue stop / start when the interface is down
We seem to be missing a netif_running() check from the devmem installation path. Starting a queue on a stopped device makes no sense. We still want to be able to allocate the memory, just to test that the device is indeed setting up the page pools in a memory provider compatible way. This is not a bug fix, because existing drivers check if the interface is down as part of the ops. But new drivers shouldn't have to do this, as long as they can correctly alloc/free while down. Reviewed-by: Mina Almasry <almasrymina@google.com> Link: https://patch.msgid.link/20250206225638.1387810-3-kuba@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions