From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Fabiano Rosas <farosas@suse.de>, peterx@redhat.com
Subject: [PULL 0/9] Staging patches
Date: Fri, 21 Nov 2025 19:26:46 -0500 [thread overview]
Message-ID: <20251122002656.687350-1-peterx@redhat.com> (raw)
The following changes since commit 5a5b06d2f6f71d7789719b97143fc5b543bec07a:
Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2025-11-20 08:12:59 +0100)
are available in the Git repository at:
https://gitlab.com/peterx/qemu.git tags/staging-pull-request
for you to fetch changes up to 6aef825073a751215de1ed410a5c94efa675f5ca:
tests/migration-test: Use MEM_TYPE_MEMFD for memory_backend (2025-11-21 19:23:46 -0500)
----------------------------------------------------------------
Migration pull for rc2
- Zhijian's COLO regression fix (since 10.0)
- Matthew's fix to avoid crash on wrong list manipulations
- Markus's error report leak fix and cleanups
- Peter's qtest changes to merge memory_backend and use_shmem
----------------------------------------------------------------
Li Zhijian (1):
migration: Fix transition to COLO state from precopy
Markus Armbruster (3):
migration: Plug memory leaks after migrate_set_error()
migration: Use warn_reportf_err() where appropriate
migration/postcopy-ram: Improve error reporting after loadvm failure
Matthew Rosato (1):
migration: set correct list pointer when removing notifier
Peter Xu (4):
tests/migration-test: Introduce MemType
tests/migration-test: Merge shmem_opts into memory_backend
tests/migration-test: Add MEM_TYPE_SHMEM
tests/migration-test: Use MEM_TYPE_MEMFD for memory_backend
tests/qtest/migration/framework.h | 26 +++++--
migration/cpr-exec.c | 3 +-
migration/migration.c | 6 +-
migration/multifd.c | 6 +-
migration/postcopy-ram.c | 17 ++---
tests/qtest/migration/cpr-tests.c | 8 +-
tests/qtest/migration/framework.c | 113 ++++++++++++++++++++---------
tests/qtest/migration/misc-tests.c | 2 +-
8 files changed, 121 insertions(+), 60 deletions(-)
--
2.50.1
next reply other threads:[~2025-11-22 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 0:26 Peter Xu [this message]
2025-11-22 0:26 ` [PULL 1/9] migration: Fix transition to COLO state from precopy Peter Xu
2025-11-22 0:26 ` [PULL 2/9] migration: set correct list pointer when removing notifier Peter Xu
2025-11-22 0:26 ` [PULL 3/9] migration: Plug memory leaks after migrate_set_error() Peter Xu
2025-11-22 0:26 ` [PULL 4/9] migration: Use warn_reportf_err() where appropriate Peter Xu
2025-11-22 0:26 ` [PULL 5/9] migration/postcopy-ram: Improve error reporting after loadvm failure Peter Xu
2025-11-22 0:26 ` [PULL 6/9] tests/migration-test: Introduce MemType Peter Xu
2025-11-22 0:26 ` [PULL 7/9] tests/migration-test: Merge shmem_opts into memory_backend Peter Xu
2025-11-22 0:26 ` [PULL 8/9] tests/migration-test: Add MEM_TYPE_SHMEM Peter Xu
2025-11-22 0:26 ` [PULL 9/9] tests/migration-test: Use MEM_TYPE_MEMFD for memory_backend 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=20251122002656.687350-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--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).