From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: Markus Armbruster <armbru@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"eblake@redhat.com" <eblake@redhat.com>,
Max Reitz <mreitz@redhat.com>,
"libvir-list@redhat.com" <libvir-list@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>, Fam Zheng <fam@euphon.net>
Subject: Re: [Qemu-devel] [PATCH v3 02/10] block/dirty-bitmaps: rename frozen predicate helper
Date: Mon, 25 Feb 2019 15:09:47 -0500 [thread overview]
Message-ID: <c59d4eb8-8c48-d003-002a-adf233268c96@redhat.com> (raw)
In-Reply-To: <8d518b5f-81ff-e8b1-c120-bca14fcf29ca@virtuozzo.com>
On 2/25/19 2:01 AM, Vladimir Sementsov-Ogievskiy wrote:
> 23.02.2019 3:06, John Snow wrote:
>> "Frozen" was a good description a long time ago, but it isn't adequate now.
>> Rename the frozen predicate to has_successor to make the semantics of the
>> predicate more clear to outside callers.
>>
>> In the process, remove some calls to frozen() that no longer semantically
>> make sense. For bdrv_enable_dirty_bitmap_locked and
>> bdrv_disable_dirty_bitmap_locked, it doesn't make sense to prohibit QEMU
>> internals from performing this action when we only wished to prohibit QMP
>> users from issuing these commands. All of the QMP API commands for bitmap
>> manipulation already check against user_locked() to prohibit these actions.
>>
>> Several other assertions really want to check that the bitmap isn't in-use
>> by another operation -- use the bitmap_user_locked function for this instead,
>> which presently also checks for has_successor. This leaves some redundant
>> checks of has_sucessor through different helpers that are addressed in
>> forthcoming patches.
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>> block/dirty-bitmap.c | 32 +++++++++++++++++---------------
>> include/block/dirty-bitmap.h | 2 +-
>> migration/block-dirty-bitmap.c | 2 +-
>> 3 files changed, 19 insertions(+), 17 deletions(-)
>>
>> diff --git a/block/dirty-bitmap.c b/block/dirty-bitmap.c
>> index 101383b3af..aa3f86bb73 100644
>> --- a/block/dirty-bitmap.c
>> +++ b/block/dirty-bitmap.c
>
> [..]
>
>> @@ -285,7 +288,7 @@ void bdrv_dirty_bitmap_enable_successor(BdrvDirtyBitmap *bitmap)
>> static void bdrv_release_dirty_bitmap_locked(BdrvDirtyBitmap *bitmap)
>> {
>> assert(!bitmap->active_iterators);
>> - assert(!bdrv_dirty_bitmap_frozen(bitmap));
>> + assert(!bdrv_dirty_bitmap_user_locked(bitmap));
>
> hmm. I'd prefere to keep a separate assertion for successor: we don't free it here,
> so we really depend on absence of this object.
>
Reasonable.
>> assert(!bitmap->meta);
>> QLIST_REMOVE(bitmap, list);
>> hbitmap_free(bitmap->bitmap);
>> @@ -325,7 +328,7 @@ BdrvDirtyBitmap *bdrv_dirty_bitmap_abdicate(BlockDriverState *bs,
>> /**
>> * In cases of failure where we can no longer safely delete the parent,
>> * we may wish to re-join the parent and child/successor.
>> - * The merged parent will be un-frozen, but not explicitly re-enabled.
>> + * The merged parent will not be user_locked, nor explicitly re-enabled.
>> * Called within bdrv_dirty_bitmap_lock..unlock and with BQL taken.
>> */
>> BdrvDirtyBitmap *bdrv_reclaim_dirty_bitmap_locked(BlockDriverState *bs,
>> @@ -373,7 +376,7 @@ void bdrv_dirty_bitmap_truncate(BlockDriverState *bs, int64_t bytes)
>>
>> bdrv_dirty_bitmaps_lock(bs);
>> QLIST_FOREACH(bitmap, &bs->dirty_bitmaps, list) {
>> - assert(!bdrv_dirty_bitmap_frozen(bitmap));
>> + assert(!bdrv_dirty_bitmap_user_locked(bitmap));
>
> and here too. As we don't truncate successors.
>
>> assert(!bitmap->active_iterators);
>> hbitmap_truncate(bitmap->bitmap, bytes);
>> bitmap->size = bytes;
>> @@ -391,7 +394,7 @@ void bdrv_release_dirty_bitmap(BlockDriverState *bs, BdrvDirtyBitmap *bitmap)
>>
>> /**
>> * Release all named dirty bitmaps attached to a BDS (for use in bdrv_close()).
>> - * There must not be any frozen bitmaps attached.
>> + * There must not be any user_locked bitmaps attached.
>> * This function does not remove persistent bitmaps from the storage.
>> * Called with BQL taken.
>> */
>> @@ -428,7 +431,6 @@ void bdrv_remove_persistent_dirty_bitmap(BlockDriverState *bs,
>> void bdrv_disable_dirty_bitmap(BdrvDirtyBitmap *bitmap)
>> {
>> bdrv_dirty_bitmap_lock(bitmap);
>> - assert(!bdrv_dirty_bitmap_frozen(bitmap));
>> bitmap->disabled = true;
>> bdrv_dirty_bitmap_unlock(bitmap);
>> }
>> diff --git a/include/block/dirty-bitmap.h b/include/block/dirty-bitmap.h
>> index 04a117fc81..cdbb4dfefd 100644
>> --- a/include/block/dirty-bitmap.h
>> +++ b/include/block/dirty-bitmap.h
>
> Could you please add scripts/git.orderfile to your .git/config, like
>
> [diff]
> orderFile = /path/to/scripts/git.orderfile
>
> ?
>
Hm, we should add this to the .gitpublish profile, but yes, let me
re-add this.
>> @@ -36,7 +36,7 @@ BlockDirtyInfoList *bdrv_query_dirty_bitmaps(BlockDriverState *bs);
>> uint32_t bdrv_get_default_bitmap_granularity(BlockDriverState *bs);
>> uint32_t bdrv_dirty_bitmap_granularity(const BdrvDirtyBitmap *bitmap);
>> bool bdrv_dirty_bitmap_enabled(BdrvDirtyBitmap *bitmap);
>> -bool bdrv_dirty_bitmap_frozen(BdrvDirtyBitmap *bitmap);
>> +bool bdrv_dirty_bitmap_has_successor(BdrvDirtyBitmap *bitmap);
>> const char *bdrv_dirty_bitmap_name(const BdrvDirtyBitmap *bitmap);
>> int64_t bdrv_dirty_bitmap_size(const BdrvDirtyBitmap *bitmap);
>> DirtyBitmapStatus bdrv_dirty_bitmap_status(BdrvDirtyBitmap *bitmap);
>> diff --git a/migration/block-dirty-bitmap.c b/migration/block-dirty-bitmap.c
>> index 6426151e4f..ac6954142f 100644
>> --- a/migration/block-dirty-bitmap.c
>> +++ b/migration/block-dirty-bitmap.c
>> @@ -542,7 +542,7 @@ static void dirty_bitmap_load_complete(QEMUFile *f, DirtyBitmapLoadState *s)
>> }
>> }
>>
>> - if (bdrv_dirty_bitmap_frozen(s->bitmap)) {
>> + if (bdrv_dirty_bitmap_has_successor(s->bitmap)) {
>> bdrv_dirty_bitmap_lock(s->bitmap);
>> if (enabled_bitmaps == NULL) {
>> /* in postcopy */
>>
>
>
> With my suggestions or without:
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>
> And thank you for rewriting commit message, it's more clear now!
>
Thanks!
next prev parent reply other threads:[~2019-02-25 20:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 0:06 [Qemu-devel] [PATCH v3 00/10] dirty-bitmaps: deprecate @status field John Snow
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 01/10] block/dirty-bitmap: add recording and busy properties John Snow
2019-02-23 20:06 ` Eric Blake
2019-02-25 6:23 ` Vladimir Sementsov-Ogievskiy
2019-02-25 15:01 ` Vladimir Sementsov-Ogievskiy
2019-02-25 15:08 ` Eric Blake
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 02/10] block/dirty-bitmaps: rename frozen predicate helper John Snow
2019-02-23 21:10 ` Eric Blake
2019-02-25 7:01 ` Vladimir Sementsov-Ogievskiy
2019-02-25 20:09 ` John Snow [this message]
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 03/10] block/dirty-bitmap: remove set/reset assertions against enabled bit John Snow
2019-02-23 21:11 ` Eric Blake
2019-02-25 7:09 ` Vladimir Sementsov-Ogievskiy
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 04/10] block/dirty-bitmap: change semantics of enabled predicate John Snow
2019-02-23 21:14 ` Eric Blake
2019-02-25 7:39 ` Vladimir Sementsov-Ogievskiy
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 05/10] nbd: change error checking order for bitmaps John Snow
2019-02-23 21:29 ` Eric Blake
2019-02-25 7:44 ` Vladimir Sementsov-Ogievskiy
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 06/10] block/dirty-bitmap: explicitly lock bitmaps with successors John Snow
2019-02-25 7:48 ` Vladimir Sementsov-Ogievskiy
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 07/10] block/dirty-bitmaps: unify qmp_locked and user_locked calls John Snow
2019-02-23 21:32 ` Eric Blake
2019-02-25 12:03 ` Vladimir Sementsov-Ogievskiy
2019-02-25 20:37 ` John Snow
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 08/10] block/dirty-bitmaps: move comment block John Snow
2019-02-23 21:32 ` Eric Blake
2019-02-25 12:11 ` Vladimir Sementsov-Ogievskiy
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 09/10] blockdev: remove unused paio parameter documentation John Snow
2019-02-23 21:33 ` Eric Blake
2019-02-25 12:20 ` Vladimir Sementsov-Ogievskiy
2019-02-23 0:06 ` [Qemu-devel] [PATCH v3 10/10] iotests: add busy/recording bit test to 124 John Snow
2019-02-23 22:06 ` Eric Blake
2019-02-25 20:29 ` John Snow
2019-02-25 22:08 ` [Qemu-devel] [PATCH v3 00/10] dirty-bitmaps: deprecate @status field John Snow
2019-02-27 17:45 ` no-reply
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=c59d4eb8-8c48-d003-002a-adf233268c96@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--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).