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: [kvm-unit-tests PATCH 0/2] arm/arm64: Use 'max' cpu and gic types
Date: Tue, 2 Apr 2024 14:21:53 +0200 [thread overview]
Message-ID: <20240402122153.101931-4-andrew.jones@linux.dev> (raw)
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.
Andrew Jones (2):
arm/arm64: Use 'max' gic type
arm64: Use 'max' cpu type
arm/run | 8 +-------
configure | 2 +-
2 files changed, 2 insertions(+), 8 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-02 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 12:21 Andrew Jones [this message]
2024-04-02 12:21 ` [kvm-unit-tests PATCH 1/2] arm/arm64: Use 'max' gic type Andrew Jones
2024-04-02 12:21 ` [kvm-unit-tests PATCH 2/2] arm64: Use 'max' cpu type Andrew Jones
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=20240402122153.101931-4-andrew.jones@linux.dev \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).