From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, andrey.shinkevich@virtuozzo.com,
vsementsov@virtuozzo.com, Fam Zheng <fam@euphon.net>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] dirty-bitmap: Expose persistent flag to 'query-block'
Date: Mon, 4 Feb 2019 14:59:48 -0500 [thread overview]
Message-ID: <509c2192-a078-78a6-70db-278f500853cc@redhat.com> (raw)
In-Reply-To: <20190204160928.11209-1-eblake@redhat.com>
On 2/4/19 11:09 AM, Eric Blake wrote:
> Since qemu currently doesn't flush persistent bitmaps to disk until
> shutdown (which might be MUCH later), it's useful if 'query-block'
> at least shows WHICH bitmaps will (eventually) make it to persistent
> storage.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> qapi/block-core.json | 5 ++++-
> block/dirty-bitmap.c | 1 +
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index dae5c7b4d83..2e0bd3c245a 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -450,11 +450,14 @@
> #
> # @status: current status of the dirty bitmap (since 2.4)
> #
> +# @persistent: true if the bitmap will eventually be flushed to persistent
> +# storage (since 4.0)
> +#
> # Since: 1.3
> ##
> { 'struct': 'BlockDirtyInfo',
> 'data': {'*name': 'str', 'count': 'int', 'granularity': 'uint32',
> - 'status': 'DirtyBitmapStatus'} }
> + 'status': 'DirtyBitmapStatus', 'persistent': 'bool' } }
>
> ##
> # @Qcow2BitmapInfoFlags:
> diff --git a/block/dirty-bitmap.c b/block/dirty-bitmap.c
> index 00ea36f5545..e46f72b346c 100644
> --- a/block/dirty-bitmap.c
> +++ b/block/dirty-bitmap.c
> @@ -440,6 +440,7 @@ BlockDirtyInfoList *bdrv_query_dirty_bitmaps(BlockDriverState *bs)
> info->has_name = !!bm->name;
> info->name = g_strdup(bm->name);
> info->status = bdrv_dirty_bitmap_status(bm);
> + info->persistent = bm->persistent;
> entry->value = info;
> *plist = entry;
> plist = &entry->next;
>
Oh, this needs a change to 236, too.
--js
prev parent reply other threads:[~2019-02-04 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 16:09 [Qemu-devel] [PATCH] dirty-bitmap: Expose persistent flag to 'query-block' Eric Blake
2019-02-04 16:23 ` Vladimir Sementsov-Ogievskiy
2019-02-04 19:30 ` John Snow
2019-02-04 19:59 ` John Snow [this message]
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=509c2192-a078-78a6-70db-278f500853cc@redhat.com \
--to=jsnow@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.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).