From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
Bandan Das <bdas@redhat.com>, Zhijian Li <lizhijian@fujitsu.com>,
Fabiano Rosas <farosas@suse.de>,
Jiri Denemark <jdenemar@redhat.com>,
Prasad Pandit <ppandit@redhat.com>,
Eric Blake <eblake@redhat.com>,
peterx@redhat.com
Subject: [PATCH v3 00/11] migration: New postcopy state, and some cleanups
Date: Wed, 19 Jun 2024 18:30:35 -0400 [thread overview]
Message-ID: <20240619223046.1798968-1-peterx@redhat.com> (raw)
Based-on: <20240617185731.9725-1-farosas@suse.de>
v3:
- Added one comment in patch 8 explaining why migrate_incoming_qmp() needs
to keep enabling "events" capability.
- Split patch 9 into two patches, which makes migration_event_wait() to be
used also in migrate_incoming_qmp()
- Rename the tests in last patch, and a spell fix
- Rebased to "[PATCH v3 00/16] migration/mapped-ram: Add direct-io support"
v1: https://lore.kernel.org/r/20240612144228.1179240-1-peterx@redhat.com
v2: https://lore.kernel.org/r/20240617181534.1425179-1-peterx@redhat.com
The major goal of this patchset is patch 5, which introduced a new postcopy
state so that we will send an event in postcopy reconnect failures that
Libvirt would prefer to have. There's more information for that issue in
the commit message alone.
Patch 1-2 are cleanups that are not directly relevant but I found/stored
that could be good to have. I made it simple by putting them together in
one thread to make patch management easier, but I can send them separately
when necessary.
Patch 3 is also a cleanup, but will be needed for patch 4 as dependency.
Patch 4-5 is the core patches.
Patch 6 updates doc for the new state.
Patch 7-11 adds a new test for the new state.
CI: https://gitlab.com/peterx/qemu/-/pipelines/1339544694
Comments welcomed, thanks.
Peter Xu (11):
migration/multifd: Avoid the final FLUSH in complete()
migration: Rename thread debug names
migration: Use MigrationStatus instead of int
migration: Cleanup incoming migration setup state change
migration/postcopy: Add postcopy-recover-setup phase
migration/docs: Update postcopy recover session for SETUP phase
tests/migration-tests: Drop most WIN32 ifdefs for postcopy failure
tests
tests/migration-tests: Always enable migration events
tests/migration-tests: migration_event_wait()
tests/migration-tests: Verify postcopy-recover-setup status
tests/migration-tests: Cover postcopy failure on reconnect
docs/devel/migration/postcopy.rst | 31 ++++----
qapi/migration.json | 4 ++
migration/migration.h | 9 +--
migration/postcopy-ram.h | 3 +
tests/qtest/migration-helpers.h | 2 +
migration/colo.c | 2 +-
migration/migration.c | 98 +++++++++++++++++--------
migration/multifd.c | 6 +-
migration/postcopy-ram.c | 10 ++-
migration/ram.c | 4 --
migration/savevm.c | 6 +-
tests/qtest/migration-helpers.c | 32 ++++++---
tests/qtest/migration-test.c | 116 +++++++++++++++++++++++-------
13 files changed, 229 insertions(+), 94 deletions(-)
--
2.45.0
next reply other threads:[~2024-06-19 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 22:30 Peter Xu [this message]
2024-06-19 22:30 ` [PATCH v3 01/11] migration/multifd: Avoid the final FLUSH in complete() Peter Xu
2024-06-19 22:30 ` [PATCH v3 02/11] migration: Rename thread debug names Peter Xu
2024-06-19 22:30 ` [PATCH v3 03/11] migration: Use MigrationStatus instead of int Peter Xu
2024-06-19 22:30 ` [PATCH v3 04/11] migration: Cleanup incoming migration setup state change Peter Xu
2024-06-19 22:30 ` [PATCH v3 05/11] migration/postcopy: Add postcopy-recover-setup phase Peter Xu
2024-06-19 22:30 ` [PATCH v3 06/11] migration/docs: Update postcopy recover session for SETUP phase Peter Xu
2024-06-19 22:30 ` [PATCH v3 07/11] tests/migration-tests: Drop most WIN32 ifdefs for postcopy failure tests Peter Xu
2024-06-19 22:30 ` [PATCH v3 08/11] tests/migration-tests: Always enable migration events Peter Xu
2024-06-20 13:20 ` Fabiano Rosas
2024-06-19 22:30 ` [PATCH v3 09/11] tests/migration-tests: migration_event_wait() Peter Xu
2024-06-20 13:21 ` Fabiano Rosas
2024-06-19 22:30 ` [PATCH v3 10/11] tests/migration-tests: Verify postcopy-recover-setup status Peter Xu
2024-06-20 13:21 ` Fabiano Rosas
2024-06-19 22:30 ` [PATCH v3 11/11] tests/migration-tests: Cover postcopy failure on reconnect Peter Xu
2024-06-21 17:38 ` [PATCH v3 00/11] migration: New postcopy state, and some cleanups Fabiano Rosas
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=20240619223046.1798968-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=bdas@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=jdenemar@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).