From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
pkrempa@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-block@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>, "Peter Xu" <peterx@redhat.com>,
"Fam Zheng" <fam@euphon.net>, "John Snow" <jsnow@redhat.com>
Subject: [PATCH v3 12/14] fixup! virtio-scsi: add iothread-vq-mapping parameter
Date: Tue, 11 Mar 2025 21:07:39 +0800 [thread overview]
Message-ID: <20250311130741.1047903-13-stefanha@redhat.com> (raw)
In-Reply-To: <20250311130741.1047903-1-stefanha@redhat.com>
---
hw/scsi/virtio-scsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
index 6274fb044c..9f61eb97db 100644
--- a/hw/scsi/virtio-scsi.c
+++ b/hw/scsi/virtio-scsi.c
@@ -1268,7 +1268,7 @@ static void virtio_scsi_hotunplug(HotplugHandler *hotplug_dev, DeviceState *dev,
qdev_simple_device_unplug_cb(hotplug_dev, dev, errp);
- if (s->vq_aio_context[0] != qemu_get_aio_context()) {
+ if (s->vq_aio_context[VIRTIO_SCSI_VQ_NUM_FIXED] != qemu_get_aio_context()) {
/* If other users keep the BlockBackend in the iothread, that's ok */
blk_set_aio_context(sd->conf.blk, qemu_get_aio_context(), NULL);
}
--
2.48.1
next prev parent reply other threads:[~2025-03-11 13:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:07 [PATCH v3 00/14] virtio-scsi: add iothread-vq-mapping parameter Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 01/14] scsi-disk: drop unused SCSIDiskState->bh field Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 02/14] dma: use current AioContext for dma_blk_io() Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 03/14] scsi: track per-SCSIRequest AioContext Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 04/14] scsi: introduce requests_lock Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 05/14] virtio-scsi: introduce event and ctrl virtqueue locks Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 06/14] virtio-scsi: protect events_dropped field Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 07/14] virtio-scsi: perform TMFs in appropriate AioContexts Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 08/14] virtio-blk: extract cleanup_iothread_vq_mapping() function Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 09/14] virtio-blk: tidy up iothread_vq_mapping functions Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 10/14] virtio: extract iothread-vq-mapping.h API Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 11/14] virtio-scsi: add iothread-vq-mapping parameter Stefan Hajnoczi
2025-03-11 13:07 ` Stefan Hajnoczi [this message]
2025-03-11 13:07 ` [PATCH v3 13/14] virtio-scsi: handle ctrl virtqueue in main loop Stefan Hajnoczi
2025-03-11 13:07 ` [PATCH v3 14/14] virtio-scsi: only expose cmd vqs via iothread-vq-mapping Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250311130741.1047903-13-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=david@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).