From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, Juraj Marcin <jmarcin@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: [PATCH 0/4] tests/migration-test: Introduce mem_type
Date: Mon, 17 Nov 2025 17:39:04 -0500 [thread overview]
Message-ID: <20251117223908.415965-1-peterx@redhat.com> (raw)
This is a small refactor series to merge memory_backend and use_shmem
parameters that migration-test uses to specify memory types. No rush for
having it for 10.2, but since this is test code, we can also consider it as
the current two parameters are definitely confusing..
This series will also make guest-memfd support extremely easy to add too.
Comments welcomed, thanks.
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 +++++--
tests/qtest/migration/cpr-tests.c | 8 +-
tests/qtest/migration/framework.c | 113 ++++++++++++++++++++---------
tests/qtest/migration/misc-tests.c | 2 +-
4 files changed, 104 insertions(+), 45 deletions(-)
--
2.50.1
next reply other threads:[~2025-11-17 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 22:39 Peter Xu [this message]
2025-11-17 22:39 ` [PATCH 1/4] tests/migration-test: Introduce MemType Peter Xu
2025-11-17 22:39 ` [PATCH 2/4] tests/migration-test: Merge shmem_opts into memory_backend Peter Xu
2025-11-21 12:46 ` Juraj Marcin
2025-11-21 15:32 ` Peter Xu
2025-11-17 22:39 ` [PATCH 3/4] tests/migration-test: Add MEM_TYPE_SHMEM Peter Xu
2025-11-17 22:39 ` [PATCH 4/4] tests/migration-test: Use MEM_TYPE_MEMFD for memory_backend Peter Xu
2025-11-21 17:50 ` [PATCH 0/4] tests/migration-test: Introduce mem_type 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=20251117223908.415965-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=jmarcin@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).