summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorJason Gunthorpe <jgg@nvidia.com>2026-09-21 19:35:50 -0300
committerAlex Williamson <alex@shazbot.org>2026-09-28 14:10:48 -0600
commiteeb2cc76b0b4b7cbf06ff383f755a93d7747b302 (patch)
treef123c32ce12a1837053d621fd9e08278ca167e36 /tools/perf/scripts/python/stackcollapse.py
parent4fdbdaf53fc8a47ef7bb3d97c0ab7afb0cf75ae2 (diff)
downloadlinux-next-eeb2cc76b0b4b7cbf06ff383f755a93d7747b302.tar.gz
linux-next-eeb2cc76b0b4b7cbf06ff383f755a93d7747b302.zip
vfio: selftests: mlx5 driver - add send_msi support
Wire an MSI-X vector to a dedicated EQ so the mlx5 driver supports send_msi(). Each EQ can be linked to an MSI-X vector, and the CQ can be set up to deliver an event to the EQ. Thus, when everything is armed, an RDMA WRITE posted to the QP generates a CQE, which generates an EQE, which generates an MSI-X. To keep things simple this just re-uses all the existing QPs and CQs, so they generate single MSIs during memcpy. send_msi() drains any accumulated MSI EQ events from prior memcpy completions, posts a small signaled RDMA Write, then polls the CQ to consume the resulting CQE (avoiding stale completions on subsequent test cycles). Assisted-by: Claude:claude-opus-4.6 Acked-by: David Matlack <dmatlack@google.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com> Link: https://lore.kernel.org/r/10-v7-c6d30e8ce1e4+3dfa6-mlx5st_jgg@nvidia.com Signed-off-by: Alex Williamson <alex@shazbot.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions