From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/5] commit: Support multiple roots above top node
Date: Mon, 25 Sep 2017 16:02:43 -0400 [thread overview]
Message-ID: <b384fd86-52e4-8468-f0d7-f9ab8c4a9e01@redhat.com> (raw)
In-Reply-To: <20170925122808.14561-1-kwolf@redhat.com>
On 09/25/2017 08:28 AM, Kevin Wolf wrote:
> This is a step towards making the commit job flexible enough that it can
> work with any kind of block graph. Currently, it requires that not only
> the top and base node of the commit operation are specified, but also
> the active layer of the backing file chain. Of course, the assumption
> that a single active layer exists is invalid.
>
> This series makes the commit job consider other roots as well so that
> all parent nodes of the top node get their backing file updated and stay
> valid after the commit job completes.
>
> With this, we should have all of the prerequisites for a follow-up
> series that adds a new and clean blockdev-commit QMP command which
> doesn't require an option for the active layer and which accepts node
> names instead of file names for base and top.
>
> Kevin Wolf (5):
> block: Introduce BdrvChildRole.update_filename
> commit: Support multiple roots above top node
> qemu-iotests: Allow QMP pretty printing in common.qemu
> qemu-iotests: Test commit block job where top has two parents
> commit: Remove overlay_bs
>
> include/block/block.h | 3 +-
> include/block/block_int.h | 6 +
> block.c | 91 +++--
> block/commit.c | 64 +---
> tests/qemu-iotests/030 | 4 -
> tests/qemu-iotests/191 | 152 ++++++++
> tests/qemu-iotests/191.out | 827 +++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/common.qemu | 14 +-
> tests/qemu-iotests/group | 1 +
> 9 files changed, 1078 insertions(+), 84 deletions(-)
> create mode 100755 tests/qemu-iotests/191
> create mode 100644 tests/qemu-iotests/191.out
>
Does this depend on another series?
next prev parent reply other threads:[~2017-09-25 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 12:28 [Qemu-devel] [PATCH 0/5] commit: Support multiple roots above top node Kevin Wolf
2017-09-25 12:28 ` [Qemu-devel] [PATCH 1/5] block: Introduce BdrvChildRole.update_filename Kevin Wolf
2017-09-25 17:58 ` Eric Blake
2017-09-25 12:28 ` [Qemu-devel] [PATCH 2/5] commit: Support multiple roots above top node Kevin Wolf
2017-09-25 19:38 ` Eric Blake
2017-09-26 17:35 ` Kevin Wolf
2017-09-25 12:28 ` [Qemu-devel] [PATCH 3/5] qemu-iotests: Allow QMP pretty printing in common.qemu Kevin Wolf
2017-09-25 19:43 ` Eric Blake
2017-09-25 12:28 ` [Qemu-devel] [PATCH 4/5] qemu-iotests: Test commit block job where top has two parents Kevin Wolf
2017-09-25 20:19 ` Eric Blake
2017-10-05 16:28 ` Kevin Wolf
2017-09-25 12:28 ` [Qemu-devel] [PATCH 5/5] commit: Remove overlay_bs Kevin Wolf
2017-09-25 20:47 ` Eric Blake
2017-09-25 20:02 ` John Snow [this message]
2017-09-26 7:59 ` [Qemu-devel] [Qemu-block] [PATCH 0/5] commit: Support multiple roots above top node 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=b384fd86-52e4-8468-f0d7-f9ab8c4a9e01@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).