From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, nshirokovskiy@virtuozzo.com, den@openvz.org,
armbru@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qapi: add dirty-bitmaps to query-named-block-nodes result
Date: Thu, 30 May 2019 12:26:26 -0400 [thread overview]
Message-ID: <c7ef8501-0c9f-f21b-1b60-dcd7dba03557@redhat.com> (raw)
In-Reply-To: <20190530143941.241963-1-vsementsov@virtuozzo.com>
On 5/30/19 10: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(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 1defcde048..64ae1ab812 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -360,6 +360,9 @@
> # @write_threshold: configured write threshold for the device.
> # 0 if disabled. (Since 2.3)
> #
> +# @dirty-bitmaps: dirty bitmaps information (only present if node
> +# has one or more dirty bitmaps) (Since 4.1)
> +#
> # Since: 0.14.0
> #
> ##
> @@ -378,7 +381,7 @@
> '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
> '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
> '*iops_size': 'int', '*group': 'str', 'cache': 'BlockdevCacheInfo',
> - 'write_threshold': 'int' } }
> + 'write_threshold': 'int', '*dirty-bitmaps': ['BlockDirtyInfo'] } }
>
> ##
> # @BlockDeviceIoStatus:
> diff --git a/block/qapi.c b/block/qapi.c
> index 0c13c86f4e..7eefdecb29 100644
> --- a/block/qapi.c
> +++ b/block/qapi.c
> @@ -78,6 +78,11 @@ BlockDeviceInfo *bdrv_block_device_info(BlockBackend *blk,
> info->backing_file = g_strdup(bs->backing_file);
> }
>
> + if (!QLIST_EMPTY(&bs->dirty_bitmaps)) {
> + info->has_dirty_bitmaps = true;
> + info->dirty_bitmaps = bdrv_query_dirty_bitmaps(bs);
> + }
> +
> info->detect_zeroes = bs->detect_zeroes;
>
> if (blk && blk_get_public(blk)->throttle_group_member.throttle_state) {
>
So query-block uses bdrv_query_info, which calls bdrv_block_device_info,
so we'll duplicate the bitmap output when doing the old-fashioned block
query, but that's probably harmless overall.
We can continue to support the output in both places, or we could opt to
deprecate the older interface; I think this is one of the last chances
we'd get to do so before libvirt and wider adoption.
I think that's probably Eric's choice.
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2019-05-30 16:29 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
2019-05-30 16:26 ` John Snow [this message]
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=c7ef8501-0c9f-f21b-1b60-dcd7dba03557@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--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).