From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Maciej S . Szmigiero" <mail@maciej.szmigiero.name>,
peterx@redhat.com, "Cédric Le Goater" <clg@redhat.com>,
"Avihai Horon" <avihaih@nvidia.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Prasad Pandit" <ppandit@redhat.com>
Subject: [PATCH v2 0/7] migration/multifd: Some VFIO / postcopy preparations on flush
Date: Thu, 5 Dec 2024 19:58:27 -0500 [thread overview]
Message-ID: <20241206005834.1050905-1-peterx@redhat.com> (raw)
CI: https://gitlab.com/peterx/qemu/-/pipelines/1575970314
Comparing to v1, this series v2 now contains some patches that may be
helpful for either VFIO or postcopy integration on top of multifd.
For VFIO, only patch 1 & 2 are relevant. This is the only part that can be
compared to v1, where I renamed the sync flag to LOCAL and ALL according to
Fabiano's comment.
For postcopy, it's about patches 3-7, but it needs to be based on 1+2.
I put them together because the two changes are relevant on the multifd
sync operation, one must depend on another in some form. So I decided to
send them together here. All these patches can be seen as cleanups /
slight optimizations on top of master branch.
This time I did more test. Besides CI, qtests, and some real-world multifd
tests just to monitor the sync events happen all correct, I made sure to
cover 7.2 machine type (which uses the legacy sync) so it still works as
before - basically sync will be more frequent, but all thing keeps working
smoothly so far.
Fabiano, let me know what do you think comparing to the other patch [1] on
simplifying the flush checks. I'm open to any comments.
Thanks,
[1] https://lore.kernel.org/r/875xo8n4ue.fsf@suse.de
Thanks,
Peter Xu (7):
migration/multifd: Further remove the SYNC on complete
migration/multifd: Allow to sync with sender threads only
migration/ram: Move RAM_SAVE_FLAG* into ram.h
migration/multifd: Unify RAM_SAVE_FLAG_MULTIFD_FLUSH messages
migration/multifd: Remove sync processing on postcopy
migration/multifd: Cleanup src flushes on condition check
migration/multifd: Document the reason to sync for save_setup()
migration/multifd.h | 23 ++++++++--
migration/ram.h | 25 +++++++++++
migration/rdma.h | 7 ---
migration/multifd-nocomp.c | 74 ++++++++++++++++++++++++++++++-
migration/multifd.c | 15 ++++---
migration/ram.c | 91 +++++++++++++++++---------------------
6 files changed, 166 insertions(+), 69 deletions(-)
--
2.47.0
next reply other threads:[~2024-12-06 1:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 0:58 Peter Xu [this message]
2024-12-06 0:58 ` [PATCH v2 1/7] migration/multifd: Further remove the SYNC on complete Peter Xu
2024-12-06 13:17 ` Fabiano Rosas
2024-12-06 14:40 ` Peter Xu
2024-12-06 0:58 ` [PATCH v2 2/7] migration/multifd: Allow to sync with sender threads only Peter Xu
2024-12-06 13:26 ` Fabiano Rosas
2024-12-06 14:50 ` Peter Xu
2024-12-06 15:00 ` Fabiano Rosas
2024-12-06 0:58 ` [PATCH v2 3/7] migration/ram: Move RAM_SAVE_FLAG* into ram.h Peter Xu
2024-12-06 13:43 ` Fabiano Rosas
2024-12-06 15:03 ` Peter Xu
2024-12-06 15:10 ` Fabiano Rosas
2024-12-06 15:46 ` Peter Xu
2024-12-06 16:58 ` Fabiano Rosas
2024-12-06 0:58 ` [PATCH v2 4/7] migration/multifd: Unify RAM_SAVE_FLAG_MULTIFD_FLUSH messages Peter Xu
2024-12-06 14:12 ` Fabiano Rosas
2024-12-06 0:58 ` [PATCH v2 5/7] migration/multifd: Remove sync processing on postcopy Peter Xu
2024-12-06 14:19 ` Fabiano Rosas
2024-12-06 0:58 ` [PATCH v2 6/7] migration/multifd: Cleanup src flushes on condition check Peter Xu
2024-12-06 14:18 ` Fabiano Rosas
2024-12-06 15:13 ` Peter Xu
2024-12-06 0:58 ` [PATCH v2 7/7] migration/multifd: Document the reason to sync for save_setup() Peter Xu
2024-12-06 14:40 ` Fabiano Rosas
2024-12-06 15:36 ` Peter Xu
2024-12-06 17:01 ` 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=20241206005834.1050905-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=clg@redhat.com \
--cc=farosas@suse.de \
--cc=mail@maciej.szmigiero.name \
--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).