Linux KVM/arm64 development list
 help / color / mirror / Atom feed
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 v2 3/3] arm64: Use 'max' cpu type
Date: Tue,  2 Apr 2024 15:27:43 +0200	[thread overview]
Message-ID: <20240402132739.201939-8-andrew.jones@linux.dev> (raw)
In-Reply-To: <20240402132739.201939-5-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 in order to test more modern models by
default. Let's finally do it!

(HVF's support for '-cpu max' is younger (only 2 years), but that
should also be old enough.)

Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
---
 configure | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure b/configure
index 49f047cb2d7d..078271822b10 100755
--- a/configure
+++ b/configure
@@ -273,7 +273,7 @@ fi
 [ -z "$processor" ] && processor="$arch"
 
 if [ "$processor" = "arm64" ]; then
-    processor="cortex-a57"
+    processor="max"
 elif [ "$processor" = "arm" ]; then
     processor="cortex-a15"
 fi
-- 
2.44.0


  parent reply	other threads:[~2024-04-02 13:27 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 ` Andrew Jones [this message]
2024-04-02 16:57 ` [kvm-unit-tests PATCH v2 0/2] arm/arm64: Use 'max' cpu and gic types 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=20240402132739.201939-8-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