From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>
Subject: [PULL v2 0/3] Migration patches for 2025-03-10
Date: Mon, 10 Mar 2025 19:34:37 -0300 [thread overview]
Message-ID: <20250310223440.31328-1-farosas@suse.de> (raw)
The following changes since commit 5136598e2667f35ef3dc1d757616a266bd5eb3a2:
Merge tag 'accel-cpus-20250309' of https://github.com/philmd/qemu into staging (2025-03-10 13:40:48 +0800)
are available in the Git repository at:
https://gitlab.com/farosas/qemu.git tags/migration-20250310-pull-request
for you to fetch changes up to baa41af1c083446971feac39b0da845e547ca068:
migration: Prioritize RDMA in ram_save_target_page() (2025-03-10 12:09:24 -0300)
----------------------------------------------------------------
Migration pull request
- Fix use-after-free in incoming migration
- Improve cpr migration blocker for volatile ram
- Fix RDMA migration
----------------------------------------------------------------
Li Zhijian (1):
migration: Prioritize RDMA in ram_save_target_page()
Peter Xu (1):
migration: Fix UAF for incoming migration on MigrationState
Steve Sistare (1):
migration: ram block cpr blockers
include/exec/memory.h | 3 ++
include/exec/ramblock.h | 1 +
migration/migration.c | 40 +++++++++++++++++++++++--
migration/ram.c | 9 +++---
migration/savevm.c | 2 ++
system/physmem.c | 66 +++++++++++++++++++++++++++++++++++++++++
6 files changed, 115 insertions(+), 6 deletions(-)
--
2.35.3
next reply other threads:[~2025-03-10 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 22:34 Fabiano Rosas [this message]
2025-03-10 22:34 ` [PULL v2 1/3] migration: Fix UAF for incoming migration on MigrationState Fabiano Rosas
2025-03-10 22:34 ` [PULL v2 2/3] migration: ram block cpr blockers Fabiano Rosas
2025-03-10 22:34 ` [PULL v2 3/3] migration: Prioritize RDMA in ram_save_target_page() Fabiano Rosas
2025-03-11 5:04 ` [PULL v2 0/3] Migration patches for 2025-03-10 Stefan Hajnoczi
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=20250310223440.31328-1-farosas@suse.de \
--to=farosas@suse.de \
--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).