qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL 0/9] Block patches
Date: Tue, 28 Jun 2016 14:23:22 +0100	[thread overview]
Message-ID: <1467120211-26495-1-git-send-email-stefanha@redhat.com> (raw)

The following changes since commit fdc997ef54c5b2c3483969aee5f1d5f2a7587520:

  target-alpha: Avoid gcc 6.1 werror for linux-user (2016-06-27 21:03:58 +0100)

are available in the git repository at:

  git://github.com/stefanha/qemu.git tags/block-pull-request

for you to fetch changes up to 2f2705908fc4b7be868d45b7b02159fb243a8457:

  virtio-blk: add num-queues device property (2016-06-28 13:08:32 +0100)

----------------------------------------------------------------

----------------------------------------------------------------

Stefan Hajnoczi (9):
  Revert "virtio: sync the dataplane vring state to the virtqueue before
    virtio_save"
  dma-helpers: dma_blk_io() cancel support
  virtio-blk: add VirtIOBlockConf->num_queues
  virtio-blk: multiqueue batch notify
  virtio-blk: tell dataplane which vq to notify
  virtio-blk: associate request with a virtqueue
  virtio-blk: live migrate s->rq with multiqueue
  virtio-blk: dataplane multiqueue support
  virtio-blk: add num-queues device property

 dma-helpers.c                   |  7 ++++
 hw/block/dataplane/virtio-blk.c | 81 +++++++++++++++++++++++++++++------------
 hw/block/dataplane/virtio-blk.h |  2 +-
 hw/block/virtio-blk.c           | 57 +++++++++++++++++++++--------
 hw/scsi/virtio-scsi.c           |  5 ---
 include/hw/virtio/virtio-blk.h  |  6 ++-
 6 files changed, 112 insertions(+), 46 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-06-28 13:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 13:23 Stefan Hajnoczi [this message]
2016-06-28 13:23 ` [Qemu-devel] [PULL 1/9] Revert "virtio: sync the dataplane vring state to the virtqueue before virtio_save" Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 2/9] dma-helpers: dma_blk_io() cancel support Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 3/9] virtio-blk: add VirtIOBlockConf->num_queues Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 4/9] virtio-blk: multiqueue batch notify Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 5/9] virtio-blk: tell dataplane which vq to notify Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 6/9] virtio-blk: associate request with a virtqueue Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 7/9] virtio-blk: live migrate s->rq with multiqueue Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 8/9] virtio-blk: dataplane multiqueue support Stefan Hajnoczi
2016-06-28 13:23 ` [Qemu-devel] [PULL 9/9] virtio-blk: add num-queues device property Stefan Hajnoczi
2016-06-28 14:03 ` [Qemu-devel] [PULL 0/9] Block patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2019-02-11  5:50 Stefan Hajnoczi
2019-02-11 11:42 ` Peter Maydell
2017-02-21 15:40 Jeff Cody
2017-02-21 18:16 ` Peter Maydell
2014-02-28 18:33 Stefan Hajnoczi
2014-03-04 17:02 ` Peter Maydell
2013-03-04  9:15 Stefan Hajnoczi
2011-03-16 10:47 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=1467120211-26495-1-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=peter.maydell@linaro.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).