From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Pavel Butsykin <pbutsykin@virtuozzo.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH 1/5] virtio-pci: use ioeventfd even when KVM is disabled
Date: Thu, 15 Jun 2017 17:38:09 +0100 [thread overview]
Message-ID: <20170615163813.7255-2-stefanha@redhat.com> (raw)
In-Reply-To: <20170615163813.7255-1-stefanha@redhat.com>
Old kvm.ko versions only supported a tiny number of ioeventfds so
virtio-pci avoids ioeventfds when kvm_has_many_ioeventfds() returns 0.
Do not check kvm_has_many_ioeventfds() when KVM is disabled since it
always returns 0. Since commit 8c56c1a592b5092d91da8d8943c17777d6462a6f
("memory: emulate ioeventfd") it has been possible to use ioeventfds in
qtest or TCG mode.
This patch makes -device virtio-blk-pci,iothread=iothread0 work even
when KVM is disabled.
I have tested that virtio-blk-pci works under TCG both with and without
iothread.
Cc: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
hw/virtio/virtio-pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
index f9b7244..9f55476 100644
--- a/hw/virtio/virtio-pci.c
+++ b/hw/virtio/virtio-pci.c
@@ -1740,7 +1740,7 @@ static void virtio_pci_realize(PCIDevice *pci_dev, Error **errp)
bool pcie_port = pci_bus_is_express(pci_dev->bus) &&
!pci_bus_is_root(pci_dev->bus);
- if (!kvm_has_many_ioeventfds()) {
+ if (kvm_enabled() && !kvm_has_many_ioeventfds()) {
proxy->flags &= ~VIRTIO_PCI_FLAG_USE_IOEVENTFD;
}
--
2.9.4
next prev parent reply other threads:[~2017-06-15 16:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 16:38 [Qemu-devel] [PATCH 0/5] qemu-iotests: test savevm/loadvm iothread (and make it work!) Stefan Hajnoczi
2017-06-15 16:38 ` Stefan Hajnoczi [this message]
2017-06-16 3:26 ` [Qemu-devel] [PATCH 1/5] virtio-pci: use ioeventfd even when KVM is disabled Michael S. Tsirkin
2017-06-16 9:13 ` Stefan Hajnoczi
2017-06-16 14:12 ` Michael S. Tsirkin
2017-06-19 12:23 ` Stefan Hajnoczi
2017-06-27 8:43 ` Fam Zheng
2017-06-27 11:07 ` Kevin Wolf
2017-06-28 12:17 ` Stefan Hajnoczi
2017-06-15 16:38 ` [Qemu-devel] [PATCH 2/5] migration: hold AioContext lock for loadvm qemu_fclose() Stefan Hajnoczi
2017-06-15 16:38 ` [Qemu-devel] [PATCH 3/5] qemu-iotests: 068: extract _qemu() function Stefan Hajnoczi
2017-06-19 12:47 ` Kevin Wolf
2017-06-27 11:40 ` Eric Blake
2017-06-27 11:42 ` Eric Blake
2017-06-28 12:13 ` Stefan Hajnoczi
2017-06-28 12:50 ` Eric Blake
2017-06-28 12:57 ` Kevin Wolf
2017-06-28 14:02 ` Eric Blake
2017-06-28 14:07 ` Kevin Wolf
2017-06-15 16:38 ` [Qemu-devel] [PATCH 4/5] qemu-iotests: 068: use -drive/-device instead of -hda Stefan Hajnoczi
2017-06-15 16:38 ` [Qemu-devel] [PATCH 5/5] qemu-iotests: 068: test iothread mode Stefan Hajnoczi
2017-06-15 16:42 ` [Qemu-devel] [PATCH 0/5] qemu-iotests: test savevm/loadvm iothread (and make it work!) Stefan Hajnoczi
2017-06-19 12:26 ` Pavel Butsykin
2017-07-05 12:55 ` Stefan Hajnoczi
2017-07-05 14:04 ` Pavel Butsykin
2017-06-19 12:55 ` Kevin Wolf
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=20170615163813.7255-2-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbutsykin@virtuozzo.com \
--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).