From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Juan Quintela <quintela@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Peter Krempa <pkrempa@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: [PATCH v5 0/3] migration: Add block-bitmap-mapping parameter
Date: Thu, 20 Aug 2020 17:07:22 +0200 [thread overview]
Message-ID: <20200820150725.68687-1-mreitz@redhat.com> (raw)
RFC v1: https://lists.nongnu.org/archive/html/qemu-block/2020-05/msg00912.html
RFC v2: https://lists.nongnu.org/archive/html/qemu-block/2020-05/msg00915.html
v1: https://lists.nongnu.org/archive/html/qemu-devel/2020-06/msg09792.html
v2: https://lists.nongnu.org/archive/html/qemu-block/2020-07/msg01179.html
v3: https://lists.nongnu.org/archive/html/qemu-block/2020-07/msg01385.html
v4: https://lists.nongnu.org/archive/html/qemu-block/2020-08/msg00566.html
Branch: https://github.com/XanClic/qemu.git migration-bitmap-mapping-v5
Branch: https://git.xanclic.moe/XanClic/qemu.git migration-bitmap-mapping-v5
Hi,
This new migration parameter allows mapping block node names and bitmap
names to aliases for the purpose of block dirty bitmap migration.
This way, management tools can use different node names on the source
and destination and pass the mapping of how bitmaps are to be
transferred to qemu (on the source, the destination, or even both with
arbitrary aliases in the migration stream).
v5:
- Patch 1:
- QAPI documentation: On the destination, unmapped aliases are not
just reported and that’s it – encountering one will actually lead to
the whole rest of the bitmap migration data being discarded.
- Use sizeof_field instead of hand-coding it
- %s/255/UINT8_MAX/
- s/Unable to read bitmap name string/
Unable to read bitmap alias string/
- Cancellation on unknown incoming bitmap aliases was handled
improperly; it should be handled properly now
- Old patch 2: Dropped
- Patch 3 (was 4): Use discards instead of writes to dirty the bitmap
git-backport-diff against v4:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/3:[0040] [FC] 'migration: Add block-bitmap-mapping parameter'
002/3:[----] [--] 'iotests.py: Let wait_migration() return on failure'
003/3:[0002] [FC] 'iotests: Test node/bitmap aliases during migration'
Max Reitz (3):
migration: Add block-bitmap-mapping parameter
iotests.py: Let wait_migration() return on failure
iotests: Test node/bitmap aliases during migration
qapi/migration.json | 104 +++++-
migration/migration.h | 3 +
migration/block-dirty-bitmap.c | 412 ++++++++++++++++++++---
migration/migration.c | 30 ++
monitor/hmp-cmds.c | 30 ++
tests/qemu-iotests/300 | 595 +++++++++++++++++++++++++++++++++
tests/qemu-iotests/300.out | 5 +
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/iotests.py | 18 +-
9 files changed, 1135 insertions(+), 63 deletions(-)
create mode 100755 tests/qemu-iotests/300
create mode 100644 tests/qemu-iotests/300.out
--
2.26.2
next reply other threads:[~2020-08-20 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 15:07 Max Reitz [this message]
2020-08-20 15:07 ` [PATCH v5 1/3] migration: Add block-bitmap-mapping parameter Max Reitz
2020-08-20 15:56 ` Vladimir Sementsov-Ogievskiy
2020-08-21 0:37 ` Eric Blake
2020-08-20 15:07 ` [PATCH v5 2/3] iotests.py: Let wait_migration() return on failure Max Reitz
2020-08-20 15:07 ` [PATCH v5 3/3] iotests: Test node/bitmap aliases during migration Max Reitz
2020-08-20 16:01 ` Vladimir Sementsov-Ogievskiy
2020-08-21 0:39 ` Eric Blake
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=20200820150725.68687-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).