From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Fabiano Rosas <farosas@suse.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Hyman Huang <yong.huang@smartx.com>,
Phil Dennis-Jordan <phil@philjordan.eu>,
Peter Xu <peterx@redhat.com>
Subject: Re: [RFC PATCH 6/7] tests/qtest/migration: Run aarch64/HVF tests using GICv2
Date: Wed, 29 Jan 2025 14:39:50 +0900 [thread overview]
Message-ID: <f77e2f82-fc96-407c-9bc9-5bd4762a0d93@daynix.com> (raw)
In-Reply-To: <20250128135429.8500-7-philmd@linaro.org>
On 2025/01/28 22:54, Philippe Mathieu-Daudé wrote:
> GICv3 isn't supported on aarch64/HVF, but GICv2 is.
Commit bdb0ade663c7 ("tests/migration-test: Stick with gicv3 in aarch64
test"), which set gic-version=3, says:
> Switch to a static gic version "3" rather than using version "max",
> so that GIC should be stable now across any future QEMU binaries for
> migration-test.
> Here the version can actually be anything as long as the ABI is
> stable.
So I think we should always set gic-version=2 so that gic-version will
not vary with hosts.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> RFC: Test eventually timeouts :(
>
> tests/qtest/migration/framework.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tests/qtest/migration/framework.c b/tests/qtest/migration/framework.c
> index 5629b8ba4e3..30808de14e0 100644
> --- a/tests/qtest/migration/framework.c
> +++ b/tests/qtest/migration/framework.c
> @@ -266,7 +266,7 @@ int migrate_start(QTestState **from, QTestState **to, const char *uri,
> } else if (strcmp(arch, "aarch64") == 0) {
> memory_size = "150M";
> machine_alias = "virt";
> - machine_opts = "gic-version=3";
> + machine_opts = env->has_hvf ? "gic-version=2" : "gic-version=3";
> arch_opts = g_strdup_printf("-cpu max -kernel %s", bootpath);
> start_address = ARM_TEST_MEM_START;
> end_address = ARM_TEST_MEM_END;
> @@ -303,6 +303,8 @@ int migrate_start(QTestState **from, QTestState **to, const char *uri,
> } else {
> accel_args = "kvm";
> }
> + } else if (env->has_hvf) {
> + accel_args = "hvf";
> } else {
> assert(env->has_tcg);
> accel_args = "tcg";
next prev parent reply other threads:[~2025-01-29 5:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 13:54 [PATCH 0/7] tests/qtest/migration: Update framework to allow using HVF accelerator Philippe Mathieu-Daudé
2025-01-28 13:54 ` [PATCH 1/7] migration/dirtyrate: Do not unlock cpu_list lock twice Philippe Mathieu-Daudé
2025-01-28 14:27 ` Fabiano Rosas
2025-01-28 19:16 ` Richard Henderson
2025-01-28 13:54 ` [PATCH 2/7] tests/qtest/migration: Make 'has_dirty_ring' generic Philippe Mathieu-Daudé
2025-01-28 14:29 ` Fabiano Rosas
2025-01-28 13:54 ` [PATCH 3/7] tests/qtest/migration: Initialize MigrationTestEnv::arch early Philippe Mathieu-Daudé
2025-01-28 14:43 ` Fabiano Rosas
2025-01-28 19:20 ` Richard Henderson
2025-01-28 13:54 ` [PATCH 4/7] tests/qtest/migration: Pass accelerator arguments as machine option Philippe Mathieu-Daudé
2025-01-28 14:59 ` Fabiano Rosas
2025-01-28 19:24 ` Richard Henderson
2025-01-28 13:54 ` [PATCH 5/7] tests/qtest/migration: Add MigrationTestEnv::has_hvf field Philippe Mathieu-Daudé
2025-01-28 15:00 ` Fabiano Rosas
2025-01-28 19:25 ` Richard Henderson
2025-01-28 13:54 ` [RFC PATCH 6/7] tests/qtest/migration: Run aarch64/HVF tests using GICv2 Philippe Mathieu-Daudé
2025-01-29 5:39 ` Akihiko Odaki [this message]
2025-02-09 19:02 ` Phil Dennis-Jordan
2025-01-28 13:54 ` [PATCH 7/7] tests/qtest/migration: Allow using accelerators different of TCG / KVM Philippe Mathieu-Daudé
2025-01-28 15:04 ` Fabiano Rosas
2025-01-28 19:29 ` Richard Henderson
2025-01-28 19:50 ` Fabiano Rosas
2025-01-28 21:08 ` Richard Henderson
2025-01-28 19:26 ` Richard Henderson
2025-01-28 13:55 ` [PATCH 0/7] tests/qtest/migration: Update framework to allow using HVF accelerator Philippe Mathieu-Daudé
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=f77e2f82-fc96-407c-9bc9-5bd4762a0d93@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=phil@philjordan.eu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yong.huang@smartx.com \
/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).