diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2025-03-11 21:26:10 +0800 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2025-03-13 17:57:23 +0100 |
| commit | da6eebb33b08131d2dc7c2594f0998012fe69e2f (patch) | |
| tree | 2ee6c8a5e3d18f9921b18077efe4c7ece4c824be /docs/sphinx/qapidoc.py | |
| parent | 7d8ab5b2f77d84a21dbeb5b254e26320e1943af4 (diff) | |
| download | qemu-da6eebb33b08131d2dc7c2594f0998012fe69e2f.zip qemu-da6eebb33b08131d2dc7c2594f0998012fe69e2f.tar.gz qemu-da6eebb33b08131d2dc7c2594f0998012fe69e2f.tar.bz2 | |
virtio-scsi: perform TMFs in appropriate AioContexts
With IOThread Virtqueue Mapping there will be multiple AioContexts
processing SCSI requests. scsi_req_cancel() and other SCSI request
operations must be performed from the AioContext where the request is
running.
Introduce a virtio_scsi_defer_tmf_to_aio_context() function and the
necessary VirtIOSCSIReq->remaining refcount infrastructure to move the
TMF code into the AioContext where the request is running.
For the time being there is still just one AioContext: the main loop or
the IOThread. When the iothread-vq-mapping parameter is added in a later
patch this will be changed to per-virtqueue AioContexts.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-ID: <20250311132616.1049687-8-stefanha@redhat.com>
Tested-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'docs/sphinx/qapidoc.py')
0 files changed, 0 insertions, 0 deletions