From: Prasad Pandit <ppandit@redhat.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, farosas@suse.de, berrange@redhat.com,
Prasad Pandit <pjp@fedoraproject.org>
Subject: [PATCH v3 0/4] Allow to enable multifd and postcopy migration together
Date: Tue, 21 Jan 2025 18:40:28 +0530 [thread overview]
Message-ID: <20250121131032.1611245-1-ppandit@redhat.com> (raw)
From: Prasad Pandit <pjp@fedoraproject.org>
Hello,
* Currently Multifd and Postcopy migration can not be used together.
QEMU shows "Postcopy is not yet compatible with multifd" message.
When migrating guests with large (100's GB) RAM, Multifd threads
help to accelerate migration, but inability to use it with the
Postcopy mode delays guest start up on the destination side.
* This patch series allows to enable both Multifd and Postcopy
migration together. Precopy and Multifd threads work during
the initial guest (RAM) transfer. When migration moves to the
Postcopy phase, Multifd threads are restrained and the Postcopy
threads start to request pages from the source side.
* This series removes magic value (4-bytes) introduced in the
previous series for the Postcopy channel. And refactoring of
the 'ram_save_target_page' function is made independent of
the multifd & postcopy change.
* This series passes all existing 'tests/qtest/migration/*' test
cases and adds a new one to enable multifd channels with postcopy
migration.
v2: https://lore.kernel.org/qemu-devel/20241129122256.96778-1-ppandit@redhat.com/T/#u
v1: https://lore.kernel.org/qemu-devel/20241126115748.118683-1-ppandit@redhat.com/T/#u
v0: https://lore.kernel.org/qemu-devel/20241029150908.1136894-1-ppandit@redhat.com/T/#u
Thank you.
---
Prasad Pandit (4):
migration/multifd: move macros to multifd header
migration: refactor ram_save_target_page functions
migration: enable multifd and postcopy together
tests/qtest/migration: add postcopy test with multifd
migration/migration.c | 106 +++++++++++++++----------
migration/multifd-nocomp.c | 3 +-
migration/multifd.c | 5 --
migration/multifd.h | 5 ++
migration/options.c | 5 --
migration/ram.c | 69 +++++-----------
tests/qtest/migration/framework.c | 8 ++
tests/qtest/migration/framework.h | 3 +
tests/qtest/migration/postcopy-tests.c | 10 +++
9 files changed, 112 insertions(+), 102 deletions(-)
--
2.48.1
next reply other threads:[~2025-01-21 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 13:10 Prasad Pandit [this message]
2025-01-21 13:10 ` [PATCH v3 1/4] migration/multifd: move macros to multifd header Prasad Pandit
2025-01-21 13:10 ` [PATCH v3 2/4] migration: refactor ram_save_target_page functions Prasad Pandit
2025-01-21 13:10 ` [PATCH v3 3/4] migration: enable multifd and postcopy together Prasad Pandit
2025-01-21 13:10 ` [PATCH v3 4/4] tests/qtest/migration: add postcopy test with multifd Prasad Pandit
2025-01-21 15:47 ` Peter Xu
2025-01-22 7:56 ` Prasad Pandit
2025-01-22 16:10 ` Peter Xu
2025-01-23 11:09 ` Prasad Pandit
2025-01-24 12:45 ` Prasad Pandit
2025-01-24 15:38 ` Peter Xu
2025-01-25 12:15 ` Prasad Pandit
2025-01-21 15:50 ` [PATCH v3 0/4] Allow to enable multifd and postcopy migration together Peter Xu
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=20250121131032.1611245-1-ppandit@redhat.com \
--to=ppandit@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=pjp@fedoraproject.org \
--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).