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 1/2] arm/arm64: Use 'max' gic type
Date: Tue, 2 Apr 2024 14:21:54 +0200 [thread overview]
Message-ID: <20240402122153.101931-5-andrew.jones@linux.dev> (raw)
In-Reply-To: <20240402122153.101931-4-andrew.jones@linux.dev>
The 'max' GIC type has been supported for six years (Mar. 2018).
Ever since its introduction we've considered switching to it for the
default in the run scripts. Now, with commit 5dd20ec76ea6 ("runtime:
Update MAX_SMP probe"), we no longer always check and restrict
MAX_SMP, so we'd have better luck with configurations working by
default by finally doing the switch. Of course we also get the
benefits of testing more modern models by default and requiring less
command line modifications when converting TCG to KVM/HVF.
Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
---
arm/run | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/arm/run b/arm/run
index efdd44ce86a7..120e406fc703 100755
--- a/arm/run
+++ b/arm/run
@@ -29,13 +29,7 @@ if ! $qemu -machine '?' | grep -q 'ARM Virtual Machine'; then
exit 2
fi
-M='-machine virt'
-
-if [ "$ACCEL" = "kvm" ]; then
- if $qemu $M,\? | grep -q gic-version; then
- M+=',gic-version=host'
- fi
-fi
+M='-machine virt,gic-version=max'
if [ "$ACCEL" = "kvm" ] || [ "$ACCEL" = "hvf" ]; then
if [ "$HOST" = "aarch64" ] || [ "$HOST" = "arm" ]; then
--
2.44.0
next prev parent reply other threads:[~2024-04-02 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 12:21 [kvm-unit-tests PATCH 0/2] arm/arm64: Use 'max' cpu and gic types Andrew Jones
2024-04-02 12:21 ` Andrew Jones [this message]
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-5-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