qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: cornelia.huck@de.ibm.com, kwolf@redhat.com, pbonzini@redhat.com,
	stefanha@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/6] virtio: Merge virtio-{blk, scsi} host notifier handling paths
Date: Wed, 13 Jul 2016 13:09:42 +0800	[thread overview]
Message-ID: <1468386588-26584-1-git-send-email-famz@redhat.com> (raw)

v4: Drop patch 1. [Cornelia]
    Add the last trivial patch.

v3: Rebase to master.
    Squash 4 into 3. [Paolo]
    Add comment and commit message. [Stefan]
    Add Stefan's r-b in patch 1 and 2.

v2: Only convert virtio-{blk,scsi}. [Paolo]

The benifit of this is we don't use event_notifier_set_handler even in
non-dataplane now, which in turn makes virtio-blk and virtio-scsi follow block
layer aio context semantics. Specifically, I/O requests must come from
blk_get_aio_context(blk) events, rather than iohandler_get_aio_context(), so
that bdrv_drained_begin/end will work as expected.

Patch 4 reverts the hack (ab27c3b5e7) we added for 2.6. Lately, commit
b880481579 added another pair of bdrv_drained_begin/end so the crash cannot
happen even without ab27c3b5e7, but in order to avoid leaking requests, patch
two is still a must.

Fam Zheng (6):
  virtio: Add typedef for handle_output
  virtio: Introduce virtio_add_queue_aio
  virtio-blk: Call virtio_add_queue_aio
  virtio-scsi: Call virtio_add_queue_aio
  Revert "mirror: Workaround for unexpected iohandler events during
    completion"
  virtio-scsi: Replace HandleOutput typedef

 block/mirror.c                  |  9 ---------
 hw/block/virtio-blk.c           |  2 +-
 hw/scsi/virtio-scsi.c           | 14 ++++++-------
 hw/virtio/virtio.c              | 45 +++++++++++++++++++++++++++++++++--------
 include/hw/virtio/virtio-scsi.h |  6 ++----
 include/hw/virtio/virtio.h      |  8 ++++++--
 6 files changed, 52 insertions(+), 32 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-07-13  5:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13  5:09 Fam Zheng [this message]
2016-07-13  5:09 ` [Qemu-devel] [PATCH v4 1/6] virtio: Add typedef for handle_output Fam Zheng
2016-07-13  9:03   ` Cornelia Huck
2016-07-13  5:09 ` [Qemu-devel] [PATCH v4 2/6] virtio: Introduce virtio_add_queue_aio Fam Zheng
2016-07-13  9:07   ` Cornelia Huck
2016-07-13  5:09 ` [Qemu-devel] [PATCH v4 3/6] virtio-blk: Call virtio_add_queue_aio Fam Zheng
2016-07-13  9:09   ` Cornelia Huck
2016-07-13  5:09 ` [Qemu-devel] [PATCH v4 4/6] virtio-scsi: " Fam Zheng
2016-07-13  9:09   ` Cornelia Huck
2016-07-13  5:09 ` [Qemu-devel] [PATCH v4 5/6] Revert "mirror: Workaround for unexpected iohandler events during completion" Fam Zheng
2016-07-13  9:10   ` Cornelia Huck
2016-07-13  5:09 ` [Qemu-devel] [PATCH v4 6/6] virtio-scsi: Replace HandleOutput typedef Fam Zheng
2016-07-13  9:11   ` Cornelia Huck
2016-07-13  9:00 ` [Qemu-devel] [PATCH v4 0/6] virtio: Merge virtio-{blk, scsi} host notifier handling paths Cornelia Huck
2016-07-13 10:32 ` Paolo Bonzini
2016-07-14 12:18   ` Stefan Hajnoczi
2016-07-14 12:18 ` 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=1468386588-26584-1-git-send-email-famz@redhat.com \
    --to=famz@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).