From: Andrew Jones <andrew.jones@linux.dev>
To: kvmarm@lists.linux.dev
Cc: alexandru.elisei@arm.com, eric.auger@redhat.com,
nikos.nikoleris@arm.com, shahuang@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 0/2] arm/arm64: Use 'max' cpu and gic types
Date: Tue, 2 Apr 2024 18:57:50 +0200 [thread overview]
Message-ID: <20240402-ef9dd0d5f92689db7e704d8c@orel> (raw)
In-Reply-To: <20240402132739.201939-5-andrew.jones@linux.dev>
On Tue, Apr 02, 2024 at 03:27:40PM +0200, Andrew Jones wrote:
> The arm64 'max' CPU type enables all features, so it makes sense to use
> it for testing to ensure we're testing the latest models. The 'max' GIC
> is used to pick the latest GIC model by default which is better than
> defaulting to gicv2 since it tests a later model and, when more
> than 8 CPUs are configured, it'll actually work. We don't need to
> convert 'max' to 'host' with KVM/HVF since 'max' is an alias for
> 'host' when those accelerators are enabled.
>
> v2:
> - Forgot to test with efi on v1 and testing now found an issue.
> Add a patch to allow '-cpu max', which has LPA2, to work with efi.
>
> Andrew Jones (3):
> arm64: Prepare for LPA2
> arm/arm64: Use 'max' gic type
> arm64: Use 'max' cpu type
>
> arm/run | 8 +------
> configure | 2 +-
> lib/arm64/asm/processor.h | 49 +++++++++++++++++++++------------------
> 3 files changed, 29 insertions(+), 30 deletions(-)
>
> --
> 2.44.0
>
I see our gitlab CI is failing for a branch with these patches. That's
because the QEMU used is pretty old on the CI and it doesn't have
commit 312b71abce30 ("target/arm: Limit LPA2 effective output address
when TCR.DS == 0"). I either need to force the CI to use 'cortex-a57',
like it always did before (and would be similar to how I've forced
riscv to use 'rv64'), or we should update the CI to use a later QEMU.
Thanks,
drew
prev parent reply other threads:[~2024-04-02 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 13:27 [kvm-unit-tests PATCH v2 0/2] arm/arm64: Use 'max' cpu and gic types Andrew Jones
2024-04-02 13:27 ` [kvm-unit-tests PATCH v2 1/3] arm64: Prepare for LPA2 Andrew Jones
2024-04-03 8:50 ` Nikos Nikoleris
2024-04-09 11:54 ` Eric Auger
2024-05-10 15:06 ` Andrew Jones
2024-04-02 13:27 ` [kvm-unit-tests PATCH v2 2/3] arm/arm64: Use 'max' gic type Andrew Jones
2024-04-02 13:27 ` [kvm-unit-tests PATCH v2 3/3] arm64: Use 'max' cpu type Andrew Jones
2024-04-02 16:57 ` Andrew Jones [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=20240402-ef9dd0d5f92689db7e704d8c@orel \
--to=andrew.jones@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=eric.auger@redhat.com \
--cc=kvmarm@lists.linux.dev \
--cc=nikos.nikoleris@arm.com \
--cc=shahuang@redhat.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