From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] Drop virtio-{blk,scsi} op blockers
Date: Wed, 18 May 2016 16:24:07 +0800 [thread overview]
Message-ID: <1463559850-5244-1-git-send-email-famz@redhat.com> (raw)
We are ready to get rid of dataplane's op blockers altogether. Most operations
are already unblocked in virtio-blk, and those remained for virtio-scsi only
because we haven't got around to add counterpart unblocking code.
The first patch fixes an existing bug with blockdev-backup. Then the op
blockers are removed from both devices.
Fam Zheng (3):
blockdev-backup: Don't move target AioContext if it's attached
virtio-blk: Remove op blocker for dataplane
virtio-scsi: Remove op blocker for dataplane
blockdev.c | 12 +++++++-
hw/block/dataplane/virtio-blk.c | 63 -----------------------------------------
hw/scsi/virtio-scsi.c | 62 ----------------------------------------
include/hw/virtio/virtio-scsi.h | 11 -------
4 files changed, 11 insertions(+), 137 deletions(-)
--
2.8.2
next reply other threads:[~2016-05-18 8:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 8:24 Fam Zheng [this message]
2016-05-18 8:24 ` [Qemu-devel] [PATCH 1/3] blockdev-backup: Don't move target AioContext if it's attached Fam Zheng
2016-05-19 20:42 ` Stefan Hajnoczi
2016-05-23 1:09 ` Fam Zheng
2016-05-20 8:03 ` Kevin Wolf
2016-05-23 1:00 ` Fam Zheng
2016-05-18 8:24 ` [Qemu-devel] [PATCH 2/3] virtio-blk: Remove op blocker for dataplane Fam Zheng
2016-05-18 8:26 ` Michael S. Tsirkin
2016-05-18 8:24 ` [Qemu-devel] [PATCH 3/3] virtio-scsi: " Fam Zheng
2016-05-18 8:26 ` Michael S. Tsirkin
2016-05-18 8:27 ` [Qemu-devel] [PATCH 0/3] Drop virtio-{blk,scsi} op blockers Michael S. Tsirkin
2016-05-19 20:48 ` Stefan Hajnoczi
2016-05-19 20:55 ` 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=1463559850-5244-1-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).