* [PATCH] migration: Fix typos in bitmap migration comments
@ 2020-07-27 20:32 Eric Blake
2020-07-27 20:49 ` Vladimir Sementsov-Ogievskiy
0 siblings, 1 reply; 2+ messages in thread
From: Eric Blake @ 2020-07-27 20:32 UTC (permalink / raw)
To: qemu-devel
Cc: Fam Zheng, vsementsov, qemu-block, Juan Quintela, dgilbert,
Stefan Hajnoczi, John Snow
Noticed while reviewing the file for newer patches.
Fixes: b35ebdf076
Signed-off-by: Eric Blake <eblake@redhat.com>
---
This is trivial enough that I'll throw it in my pull request today.
migration/block-dirty-bitmap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/migration/block-dirty-bitmap.c b/migration/block-dirty-bitmap.c
index 1f675b792fc9..784330ebe130 100644
--- a/migration/block-dirty-bitmap.c
+++ b/migration/block-dirty-bitmap.c
@@ -97,7 +97,7 @@
#define DIRTY_BITMAP_MIG_START_FLAG_ENABLED 0x01
#define DIRTY_BITMAP_MIG_START_FLAG_PERSISTENT 0x02
-/* 0x04 was "AUTOLOAD" flags on elder versions, no it is ignored */
+/* 0x04 was "AUTOLOAD" flags on older versions, now it is ignored */
#define DIRTY_BITMAP_MIG_START_FLAG_RESERVED_MASK 0xf8
/* State of one bitmap during save process */
@@ -180,7 +180,7 @@ static uint32_t qemu_get_bitmap_flags(QEMUFile *f)
static void qemu_put_bitmap_flags(QEMUFile *f, uint32_t flags)
{
- /* The code currently do not send flags more than one byte */
+ /* The code currently does not send flags as more than one byte */
assert(!(flags & (0xffffff00 | DIRTY_BITMAP_MIG_EXTRA_FLAGS)));
qemu_put_byte(f, flags);
--
2.27.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] migration: Fix typos in bitmap migration comments
2020-07-27 20:32 [PATCH] migration: Fix typos in bitmap migration comments Eric Blake
@ 2020-07-27 20:49 ` Vladimir Sementsov-Ogievskiy
0 siblings, 0 replies; 2+ messages in thread
From: Vladimir Sementsov-Ogievskiy @ 2020-07-27 20:49 UTC (permalink / raw)
To: Eric Blake, qemu-devel
Cc: Fam Zheng, qemu-block, Juan Quintela, dgilbert, Stefan Hajnoczi,
John Snow
27.07.2020 23:32, Eric Blake wrote:
> Noticed while reviewing the file for newer patches.
>
> Fixes: b35ebdf076
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> This is trivial enough that I'll throw it in my pull request today.
>
> migration/block-dirty-bitmap.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/migration/block-dirty-bitmap.c b/migration/block-dirty-bitmap.c
> index 1f675b792fc9..784330ebe130 100644
> --- a/migration/block-dirty-bitmap.c
> +++ b/migration/block-dirty-bitmap.c
> @@ -97,7 +97,7 @@
>
> #define DIRTY_BITMAP_MIG_START_FLAG_ENABLED 0x01
> #define DIRTY_BITMAP_MIG_START_FLAG_PERSISTENT 0x02
> -/* 0x04 was "AUTOLOAD" flags on elder versions, no it is ignored */
> +/* 0x04 was "AUTOLOAD" flags on older versions, now it is ignored */
may be also s/flags/flag
> #define DIRTY_BITMAP_MIG_START_FLAG_RESERVED_MASK 0xf8
>
> /* State of one bitmap during save process */
> @@ -180,7 +180,7 @@ static uint32_t qemu_get_bitmap_flags(QEMUFile *f)
>
> static void qemu_put_bitmap_flags(QEMUFile *f, uint32_t flags)
> {
> - /* The code currently do not send flags more than one byte */
> + /* The code currently does not send flags as more than one byte */
Hmm, why "as more than", not just "more than"?.
(this note is about the following: the protocol allows adding more than
one byte of flags with use of DIRTY_BITMAP_MIG_EXTRA_FLAGS. Still,
currently this possibility is not used and we assert it.)
> assert(!(flags & (0xffffff00 | DIRTY_BITMAP_MIG_EXTRA_FLAGS)));
>
> qemu_put_byte(f, flags);
>
Anyway:
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
--
Best regards,
Vladimir
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-07-27 20:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-07-27 20:32 [PATCH] migration: Fix typos in bitmap migration comments Eric Blake
2020-07-27 20:49 ` Vladimir Sementsov-Ogievskiy
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).