From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com, Juraj Marcin <jmarcin@redhat.com>
Subject: Re: [PATCH 0/4] tests/migration-test: Introduce mem_type
Date: Fri, 21 Nov 2025 14:50:23 -0300 [thread overview]
Message-ID: <878qfzff6o.fsf@suse.de> (raw)
In-Reply-To: <20251117223908.415965-1-peterx@redhat.com>
Peter Xu <peterx@redhat.com> writes:
> 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(-)
Series:
Reviewed-by: Fabiano Rosas <farosas@suse.de>
prev parent reply other threads:[~2025-11-22 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 22:39 [PATCH 0/4] tests/migration-test: Introduce mem_type Peter Xu
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 ` 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=878qfzff6o.fsf@suse.de \
--to=farosas@suse.de \
--cc=jmarcin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.