From: Peter Xu <peterx@redhat.com>
To: Juraj Marcin <jmarcin@redhat.com>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH 0/2] test/qtest/migration: Use out-of-band execution for migrate-recover
Date: Tue, 7 Jan 2025 16:12:56 -0500 [thread overview]
Message-ID: <Z32Y2C0iw3gGIkkg@x1n> (raw)
In-Reply-To: <20250107163156.310226-1-jmarcin@redhat.com>
On Tue, Jan 07, 2025 at 05:31:52PM +0100, Juraj Marcin wrote:
> In real use cases, the migrate-recover command requires out-of-band
> execution, because the main thread processing normal commands is blocked
> by a page fault in the guest memory. Tests, however, do not reflect this
> which might result in some bugs not being caught with tests.
>
> The first patch in the series, adds a new qtest initialization function
> which accepts capabilities the test wants to enable. This allows a test
> to enable the oob capability.
>
> The second patch then enables the oob capability in migration tests and
> changes the execution of the migrate-recover command.
>
> Juraj Marcin (2):
> tests/qtest: Introduce qtest_init_with_env_and_capabilities()
> tests/qtest/migration: Use out-of-band execution for migrate-recover
>
> tests/qtest/libqtest.c | 18 ++++++++++++++++--
> tests/qtest/libqtest.h | 17 +++++++++++++++++
> tests/qtest/migration/framework.c | 23 +++++++++++++++++++++--
> tests/qtest/migration/framework.h | 2 ++
> tests/qtest/migration/migration-qmp.c | 2 +-
> 5 files changed, 57 insertions(+), 5 deletions(-)
Looks all good, thanks!
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2025-01-07 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 16:31 [PATCH 0/2] test/qtest/migration: Use out-of-band execution for migrate-recover Juraj Marcin
2025-01-07 16:31 ` [PATCH 1/2] tests/qtest: Introduce qtest_init_with_env_and_capabilities() Juraj Marcin
2025-01-07 16:31 ` [PATCH 2/2] tests/qtest/migration: Use out-of-band execution for migrate-recover Juraj Marcin
2025-01-07 21:12 ` Peter Xu [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=Z32Y2C0iw3gGIkkg@x1n \
--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).