From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Fabiano Rosas <farosas@suse.de>, Eric Blake <eblake@redhat.com>,
Prasad Pandit <ppandit@redhat.com>,
peterx@redhat.com, Jiri Denemark <jdenemar@redhat.com>,
Bandan Das <bdas@redhat.com>
Subject: [PATCH v2 00/10] migration: New postcopy state, and some cleanups
Date: Mon, 17 Jun 2024 14:15:24 -0400 [thread overview]
Message-ID: <20240617181534.1425179-1-peterx@redhat.com> (raw)
v2:
- Collect tags
- Patch 3
- cover all states in migration_postcopy_is_alive()
- Patch 4 (old)
- English changes [Fabiano]
- Split the migration_incoming_state_setup() cleanup into a new patch
[Fabiano]
- Drop RECOVER_SETUP in fill_destination_migration_info() [Fabiano]
- Keep using explicit state check in migrate_fd_connect() for resume
[Fabiano]
- New patches
- New doc update: "migration/docs: Update postcopy recover session for
SETUP phase"
- New test case: last four patches
v1: https://lore.kernel.org/r/20240612144228.1179240-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-10 adds a new test for the new state.
Comments welcomed, thanks.
CI: https://gitlab.com/peterx/qemu/-/pipelines/1335604588
(check-dco & check-patch fail to git-fetch, but doesn't look relevant)
Peter Xu (10):
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: 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 | 20 ++++++
tests/qtest/migration-test.c | 110 ++++++++++++++++++++++++------
13 files changed, 223 insertions(+), 82 deletions(-)
--
2.45.0
next reply other threads:[~2024-06-17 18:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 18:15 Peter Xu [this message]
2024-06-17 18:15 ` [PATCH v2 01/10] migration/multifd: Avoid the final FLUSH in complete() Peter Xu
2024-06-17 18:15 ` [PATCH v2 02/10] migration: Rename thread debug names Peter Xu
2024-06-19 1:05 ` Zhijian Li (Fujitsu) via
2024-06-17 18:15 ` [PATCH v2 03/10] migration: Use MigrationStatus instead of int Peter Xu
2024-06-17 19:38 ` Fabiano Rosas
2024-06-17 18:15 ` [PATCH v2 04/10] migration: Cleanup incoming migration setup state change Peter Xu
2024-06-17 19:41 ` Fabiano Rosas
2024-06-17 18:15 ` [PATCH v2 05/10] migration/postcopy: Add postcopy-recover-setup phase Peter Xu
2024-06-17 19:45 ` Fabiano Rosas
2024-06-17 18:15 ` [PATCH v2 06/10] migration/docs: Update postcopy recover session for SETUP phase Peter Xu
2024-06-17 19:47 ` Fabiano Rosas
2024-06-17 18:15 ` [PATCH v2 07/10] tests/migration-tests: Drop most WIN32 ifdefs for postcopy failure tests Peter Xu
2024-06-17 19:49 ` Fabiano Rosas
2024-06-17 18:15 ` [PATCH v2 08/10] tests/migration-tests: Always enable migration events Peter Xu
2024-06-17 19:51 ` Fabiano Rosas
2024-06-17 21:23 ` Peter Xu
2024-06-19 20:39 ` Peter Xu
2024-06-17 18:15 ` [PATCH v2 09/10] tests/migration-tests: Verify postcopy-recover-setup status Peter Xu
2024-06-17 19:53 ` Fabiano Rosas
2024-06-17 18:15 ` [PATCH v2 10/10] tests/migration-tests: Cover postcopy failure on reconnect Peter Xu
2024-06-17 20:07 ` Fabiano Rosas
2024-06-17 19:34 ` [PATCH v2 00/10] migration: New postcopy state, and some cleanups Peter Xu
2024-06-17 20:12 ` 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=20240617181534.1425179-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=lvivier@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).