From: Lukas Straub <lukasstraub2@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Hailiang Zhang <zhanghailiang@xfusion.com>,
Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
"Zhang, Chen" <chen.zhang@intel.com>
Subject: [PATCH 0/8] colo migration cleanups
Date: Thu, 22 Jun 2023 14:14:40 +0200 [thread overview]
Message-ID: <cover.1687429356.git.lukasstraub2@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Hello Everyone,
Here are some cleanups around the colo migration code. Notably, we only
support the same qemu version on both sides for now. Though in this
patchset I still try to be support migration to a newer qemu version.
Lukas Straub (8):
colo: Only support the same qemu version on source and destination
colo: Setup ram cache in normal migration path
colo: Replace migration_incoming_colo_enabled() with migrate_colo()
colo: Remove ENABLE_COLO loadvm command functions
colo: Don't send ENABLE_COLO command
colo: Reject colo with postcopy capability enabled
colo: Reject colo with block migration capability enabled
ram: Remove useless colo special-casing
docs/COLO-FT.txt | 2 ++
include/migration/colo.h | 3 --
migration/colo.c | 2 +-
migration/migration.c | 63 ++++++++++------------------------------
migration/options.c | 14 +++++++++
migration/ram.c | 14 ++++-----
migration/savevm.c | 21 +-------------
migration/savevm.h | 1 -
migration/trace-events | 1 -
9 files changed, 41 insertions(+), 80 deletions(-)
--
2.39.2
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-06-22 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 12:14 Lukas Straub [this message]
2023-06-22 12:15 ` [PATCH 1/8] colo: Only support the same qemu version on source and destination Lukas Straub
2023-06-22 17:17 ` Dong, Eddie
2023-06-27 9:59 ` Zhang, Chen
2023-06-22 12:15 ` [PATCH 2/8] colo: Setup ram cache in normal migration path Lukas Straub
2023-06-28 9:30 ` Zhang, Chen
2023-06-22 12:15 ` [PATCH 3/8] colo: Replace migration_incoming_colo_enabled() with migrate_colo() Lukas Straub
2023-06-22 12:15 ` [PATCH 4/8] colo: Remove ENABLE_COLO loadvm command functions Lukas Straub
2023-06-22 12:15 ` [PATCH 5/8] colo: Don't send ENABLE_COLO command Lukas Straub
2023-06-22 12:16 ` [PATCH 6/8] colo: Reject colo with postcopy capability enabled Lukas Straub
2023-06-22 12:16 ` [PATCH 7/8] colo: Reject colo with block migration " Lukas Straub
2023-06-22 12:16 ` [PATCH 8/8] ram: Remove useless colo special-casing Lukas Straub
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=cover.1687429356.git.lukasstraub2@web.de \
--to=lukasstraub2@web.de \
--cc=chen.zhang@intel.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhanghailiang@xfusion.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.