From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, qemu-devel@nongnu.org
Cc: cornelia.huck@de.ibm.com, Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PATCH V3 0/6] virtio 1.0 pci optimizations and fixes
Date: Fri, 6 Nov 2015 16:02:43 +0800 [thread overview]
Message-ID: <1446796969-8049-1-git-send-email-jasowang@redhat.com> (raw)
Hi all:
This series tries to fix the following issues:
- qemu abort when trying to adjust endianness for zero length eventfd,
this prevent fast mmio eventfd from being used in ppc. Fixing by
skip the endianness adjustment for zero length eventfd.
- 1.0 mmio is slow since it was using datamatch eventfd. Fixing this
by usinng zero length mmio eventfd, then we could get speed up through
kernel fast mmio bus on ept capable machine.
- 1.0 mmio is slow compared to pio (at least on some
archs/setups). Fixing this by re-introducing pio notification
capability. This will be useful for the arch/setups that fast mmio
does not work.
- Some virtio pci 1.0 fields were not migrated. This will cause
unexpected behaviour if migrate during driver initialization. Fixing
this by introduce a transport specific callback and get/put
transport specific fields for virtio 1.0.
- queue_enable read was broken. Fixing by set the queue_enable to true
during guest write and clear it during reset.
Please review.
Thanks
Changes from V2:
- rebase to master
- conditionally use zero length io eventfd based on new kvm cap
- replace "modern_state" with "extra_state" in patch 1
- check for the existence of k->load_extra_state in patch 1
Changes from V1:
- skip zero length eventfd endianness adjustment
- don't use pci specific name ("modern") in virtio core, using "extra"
instead and in virtio pci callback, using subsections which could
allow us to extend the future improvement without changing the core.
- don't check virtio_virtqueue_needed() in virtio_extra_state_needed()
- drop the ppc 2.5 machine type patch
- squash Eduardo's 2.5 machine type patches into this series
Jason Wang (6):
virtio-pci: fix 1.0 virtqueue migration
memory: don't try to adjust endianness for zero length eventfd
KVM: add support for any length io eventfd
virtio-pci: use zero length mmio eventfd for 1.0 notification cap when
possible
virtio-pci: introduce pio notification capability for modern device
virtio-pci: unbreak queue_enable read
hw/virtio/virtio-pci.c | 277 +++++++++++++++++++++++++++++++++++++----
hw/virtio/virtio-pci.h | 28 +++--
hw/virtio/virtio.c | 58 +++++++++
include/hw/compat.h | 4 +
include/hw/virtio/virtio-bus.h | 3 +
include/sysemu/kvm.h | 8 ++
kvm-all.c | 4 +
kvm-stub.c | 1 +
memory.c | 8 +-
9 files changed, 361 insertions(+), 30 deletions(-)
--
2.1.4
next reply other threads:[~2015-11-06 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:02 Jason Wang [this message]
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 1/6] virtio-pci: fix 1.0 virtqueue migration Jason Wang
2015-11-09 12:56 ` Cornelia Huck
2015-11-10 2:35 ` Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 2/6] memory: don't try to adjust endianness for zero length eventfd Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 3/6] KVM: add support for any length io eventfd Jason Wang
2015-11-11 11:01 ` Paolo Bonzini
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 4/6] virtio-pci: use zero length mmio eventfd for 1.0 notification cap when possible Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 5/6] virtio-pci: introduce pio notification capability for modern device Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 6/6] virtio-pci: unbreak queue_enable read Jason Wang
2015-11-09 13:14 ` Cornelia Huck
2015-11-10 2:51 ` Jason Wang
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=1446796969-8049-1-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=mst@redhat.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).