summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2026-09-12 06:30:14 -0400
committerMichael S. Tsirkin <mst@redhat.com>2026-09-12 11:58:57 -0400
commitdd75508e6fe77116589c49658d0d18897688dc0b (patch)
tree11af948967695b1904b8b43477ccd128a8cebbd0 /tools/perf/scripts/python/export-to-sqlite.py
parentdd886653d2038a510a21bff476fa1be0422a4fb9 (diff)
downloadlinux-next-dd75508e6fe77116589c49658d0d18897688dc0b.tar.gz
linux-next-dd75508e6fe77116589c49658d0d18897688dc0b.zip
virtio: synchronize callbacks after device reset
virtio_reset_device says: Note: this guarantees that vq callbacks are not in progress but in practice, only virtio pci correctly synchronizes the cbs. On other transports, a callback that is already executing, keeps running while the driver tears down the state it uses. Add virtio_synchronize_cbs to virtio_reset_device fixing this for all transports that correctly implement synchronize_cbs(). Reported-by: Karl Mehltretter <kmehltretter@gmail.com> Link: https://lore.kernel.org/all/20260818040433.66986-1-kmehltretter@gmail.com/ Fixes: c46eccdaadab ("virtio: document virtio_reset_device") Tested-by: Karl Mehltretter <kmehltretter@gmail.com> Acked-by: Karl Mehltretter <kmehltretter@gmail.com> Assisted-by: LLM Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Message-ID: <8ae2995ee649adcfe1398f7f1c4fc9f7028c3db1.1789204858.git.mst@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions