qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: qemu-devel@nongnu.org, mst@redhat.com
Cc: Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PATCH 0/6] virtio pci 1.0 optimizations and fixes
Date: Fri, 21 Aug 2015 17:05:44 +0800	[thread overview]
Message-ID: <1440147950-1178-1-git-send-email-jasowang@redhat.com> (raw)

Hi all:

This series tries to fix the following issues:

- 1.0 mmio is slow. Fixing this by usinng wildcard 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. 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

Jason Wang (6):
  pc: introduce 2.5 machine type
  ppc: spapr: introduce 2.5 machine type
  virtio-pci: fix 1.0 virtqueue migration
  virtio-pci: use wildcard mmio eventfd for 1.0 notification cap
  virtio-pci: introduce pio notification capability for modern device
  virtio-pci: unbreak queue_enable read

 hw/i386/pc_piix.c              |  21 ++++-
 hw/i386/pc_q35.c               |  23 ++++-
 hw/ppc/spapr.c                 |  40 +++++++-
 hw/virtio/virtio-pci.c         | 206 ++++++++++++++++++++++++++++++++++++-----
 hw/virtio/virtio-pci.h         |  30 ++++--
 hw/virtio/virtio.c             |  58 ++++++++++++
 include/hw/compat.h            |   7 ++
 include/hw/i386/pc.h           |   3 +
 include/hw/virtio/virtio-bus.h |   3 +
 9 files changed, 357 insertions(+), 34 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-08-21  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  9:05 Jason Wang [this message]
2015-08-21  9:05 ` [Qemu-devel] [PATCH 1/6] pc: introduce 2.5 machine type Jason Wang
2015-08-21 15:47   ` Eduardo Habkost
2015-08-24  5:45     ` Jason Wang
2015-08-21  9:05 ` [Qemu-devel] [PATCH 2/6] ppc: spapr: " Jason Wang
2015-08-22  0:10   ` David Gibson
2015-08-24  5:37     ` Jason Wang
2015-08-21  9:05 ` [Qemu-devel] [PATCH 3/6] virtio-pci: fix 1.0 virtqueue migration Jason Wang
2015-08-21  9:43   ` Cornelia Huck
2015-08-24  5:37     ` Jason Wang
2015-08-24 14:14       ` Cornelia Huck
2015-08-25  3:14         ` Jason Wang
2015-08-21  9:05 ` [Qemu-devel] [PATCH 4/6] virtio-pci: use wildcard mmio eventfd for 1.0 notification cap Jason Wang
2015-08-24 16:30   ` Greg Kurz
2015-08-25  3:21     ` Jason Wang
2015-08-21  9:05 ` [Qemu-devel] [PATCH 5/6] virtio-pci: introduce pio notification capability for modern device Jason Wang
2015-08-24 14:52   ` Greg Kurz
2015-08-24 16:29     ` Greg Kurz
2015-08-25 11:48   ` Michael S. Tsirkin
2015-08-26  5:29     ` Jason Wang
2015-08-21  9:05 ` [Qemu-devel] [PATCH 6/6] virtio-pci: unbreak queue_enable read 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=1440147950-1178-1-git-send-email-jasowang@redhat.com \
    --to=jasowang@redhat.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).