From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com, pbonzini@redhat.com,
famz@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] block: BdrvChildRole.drained_begin/end fixes
Date: Mon, 23 May 2016 18:55:11 +0200 [thread overview]
Message-ID: <1464022515-11390-1-git-send-email-kwolf@redhat.com> (raw)
While working on the series that converts block jobs to using a separate
BlockBackend, I noticed that I need to do some drain fixes first. So here they
are.
Patches 1 and 2 are just preparation, patches 3 and 4 are the actual fixes.
Kevin Wolf (4):
block: Introduce bdrv_replace_child()
block: Make bdrv_drain() use bdrv_drained_begin/end()
block: Fix reconfiguring graph with drained nodes
block: Propagate .drained_begin/end callbacks
block.c | 58 +++++++++++++++++++++++++++++++++------
block/block-backend.c | 9 ++++---
block/io.c | 69 +++++++++++++++++++++++------------------------
include/block/block_int.h | 3 ++-
4 files changed, 90 insertions(+), 49 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-05-23 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 16:55 Kevin Wolf [this message]
2016-05-23 16:55 ` [Qemu-devel] [PATCH 1/4] block: Introduce bdrv_replace_child() Kevin Wolf
2016-05-23 20:02 ` Eric Blake
2016-05-23 16:55 ` [Qemu-devel] [PATCH 2/4] block: Make bdrv_drain() use bdrv_drained_begin/end() Kevin Wolf
2016-05-23 21:10 ` Eric Blake
2016-05-23 16:55 ` [Qemu-devel] [PATCH 3/4] block: Fix reconfiguring graph with drained nodes Kevin Wolf
2016-05-23 21:17 ` Eric Blake
2016-05-23 16:55 ` [Qemu-devel] [PATCH 4/4] block: Propagate .drained_begin/end callbacks Kevin Wolf
2016-05-23 21:19 ` Eric Blake
2016-05-24 1:01 ` [Qemu-devel] [PATCH 0/4] block: BdrvChildRole.drained_begin/end fixes Fam Zheng
2016-05-24 7:33 ` 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=1464022515-11390-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=famz@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).