From: Fabiano Rosas <farosas@suse.de>
To: Li Zhijian via <qemu-devel@nongnu.org>, qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Li Zhijian <lizhijian@fujitsu.com>
Subject: Re: [PATCH v5 0/6] migration/rdma: fixes, refactor and cleanup
Date: Fri, 07 Mar 2025 11:15:40 -0300 [thread overview]
Message-ID: <8734fpudtf.fsf@suse.de> (raw)
In-Reply-To: <20250305062825.772629-1-lizhijian@fujitsu.com>
Li Zhijian via <qemu-devel@nongnu.org> writes:
> - It fix the RDMA migration broken issue
> - disable RDMA + postcopy
> - some cleanups
> - Add a qtest for RDMA at last
>
> Changes since V4:
> - collect Reviewed-tags
> - Address comments in patch "migration: Add qtest for migration over RDMA" from Fabiano Rosas <farosas@suse.de>
>
> Changes since V3:
> - check RDMA and capabilities are compatible on both sides # renamed from
> previous V3's "migration: Add migration_capabilities_and_transport_compatible()"
>
> Changes since V2:
> - squash previous 2/3/4 to '[PATCH v3 5/6] migration: Unfold control_save_page()'
> - reorder the patch layout to prevent recently added code from being deleted again.
> - collect Reviewed tags from Peter
>
> Changes since V1[0]:
> Add some saparate patches to refactor and cleanup based on V1
>
> [0] https://lore.kernel.org/qemu-devel/20250218074345.638203-1-lizhijian@fujitsu.com/
>
> Li Zhijian (6):
> migration: Prioritize RDMA in ram_save_target_page()
> migration: check RDMA and capabilities are compatible on both sides
> migration: disable RDMA + postcopy-ram
> migration/rdma: Remove redundant migration_in_postcopy checks
> migration: Unfold control_save_page()
> migration: Add qtest for migration over RDMA
>
> MAINTAINERS | 1 +
> migration/migration.c | 30 ++++++++----
> migration/options.c | 25 ++++++++++
> migration/options.h | 1 +
> migration/ram.c | 41 +++++-----------
> migration/rdma.c | 11 ++---
> migration/rdma.h | 3 +-
> scripts/rdma-migration-helper.sh | 48 +++++++++++++++++++
> tests/qtest/migration/precopy-tests.c | 67 +++++++++++++++++++++++++++
> 9 files changed, 178 insertions(+), 49 deletions(-)
> create mode 100755 scripts/rdma-migration-helper.sh
Queued, thanks!
prev parent reply other threads:[~2025-03-07 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 6:28 [PATCH v5 0/6] migration/rdma: fixes, refactor and cleanup Li Zhijian via
2025-03-05 6:28 ` [PATCH v5 1/6] migration: Prioritize RDMA in ram_save_target_page() Li Zhijian via
2025-03-05 6:28 ` [PATCH v5 2/6] migration: check RDMA and capabilities are compatible on both sides Li Zhijian via
2025-03-05 6:28 ` [PATCH v5 3/6] migration: disable RDMA + postcopy-ram Li Zhijian via
2025-03-05 6:28 ` [PATCH v5 4/6] migration/rdma: Remove redundant migration_in_postcopy checks Li Zhijian via
2025-03-05 6:28 ` [PATCH v5 5/6] migration: Unfold control_save_page() Li Zhijian via
2025-03-05 6:28 ` [PATCH v5 6/6] migration: Add qtest for migration over RDMA Li Zhijian via
2025-03-07 14:15 ` Fabiano Rosas [this message]
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=8734fpudtf.fsf@suse.de \
--to=farosas@suse.de \
--cc=lizhijian@fujitsu.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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).