From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, mreitz@redhat.com,
nshirokovskiy@virtuozzo.com, den@openvz.org, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qapi: add dirty-bitmaps to query-named-block-nodes result
Date: Thu, 30 May 2019 10:01:52 -0500 [thread overview]
Message-ID: <dd1f2ea6-9e4c-1486-7d10-da3b0a84bbc4@redhat.com> (raw)
In-Reply-To: <20190530143941.241963-1-vsementsov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
On 5/30/19 9:39 AM, Vladimir Sementsov-Ogievskiy wrote:
> Let's add a possibility to query dirty-bitmaps not only on root nodes.
> It is useful when dealing both with snapshots and incremental backups.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> qapi/block-core.json | 5 ++++-
> block/qapi.c | 5 +++++
> 2 files changed, 9 insertions(+), 1 deletion(-)
Indeed useful.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-30 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 14:39 [Qemu-devel] [PATCH] qapi: add dirty-bitmaps to query-named-block-nodes result Vladimir Sementsov-Ogievskiy
2019-05-30 15:01 ` Eric Blake [this message]
2019-05-30 16:26 ` John Snow
2019-05-31 14:55 ` Eric Blake
2019-05-31 18:22 ` John Snow
2019-06-05 12:46 ` Markus Armbruster
2019-07-16 0:13 ` John Snow
2019-07-16 6:32 ` Markus Armbruster
2019-07-16 15:26 ` John Snow
2019-07-17 15:57 ` John Snow
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=dd1f2ea6-9e4c-1486-7d10-da3b0a84bbc4@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=nshirokovskiy@virtuozzo.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).