From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: andrew.jones@linux.dev, eric.auger@redhat.com,
kvmarm@lists.linux.dev, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, vladimir.murzin@arm.com
Subject: Re: [kvm-unit-tests PATCH v3 1/5] configure: arm64: Don't display 'aarch64' as the default architecture
Date: Thu, 27 Mar 2025 17:11:23 +0000 [thread overview]
Message-ID: <Z-WGuyzy4qxAcJD4@raptor> (raw)
In-Reply-To: <20250325160031.2390504-4-jean-philippe@linaro.org>
Hi Jean-Philippe
On Tue, Mar 25, 2025 at 04:00:29PM +0000, Jean-Philippe Brucker wrote:
> From: Alexandru Elisei <alexandru.elisei@arm.com>
>
> --arch=aarch64, intentional or not, has been supported since the initial
> arm64 support, commit 39ac3f8494be ("arm64: initial drop"). However,
> "aarch64" does not show up in the list of supported architectures, but
> it's displayed as the default architecture if doing ./configure --help
> on an arm64 machine.
>
> Keep everything consistent and make sure that the default value for
> $arch is "arm64", but still allow --arch=aarch64, in case they are users
> that use this configuration for kvm-unit-tests.
You can drop this paragraph, since the change to the default value for $arch was
dropped.
With this change:
Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>
Thanks,
Alex
>
> The help text for --arch changes from:
>
> --arch=ARCH architecture to compile for (aarch64). ARCH can be one of:
> arm, arm64, i386, ppc64, riscv32, riscv64, s390x, x86_64
>
> to:
>
> --arch=ARCH architecture to compile for (arm64). ARCH can be one of:
> arm, arm64, i386, ppc64, riscv32, riscv64, s390x, x86_64
>
> Signed-off-by: Alexandru Elisei <alexandru.elisei@arm.com>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> configure | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/configure b/configure
> index 52904d3a..010c68ff 100755
> --- a/configure
> +++ b/configure
> @@ -43,6 +43,7 @@ else
> fi
>
> usage() {
> + [ "$arch" = "aarch64" ] && arch="arm64"
> cat <<-EOF
> Usage: $0 [options]
>
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-03-27 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 16:00 [kvm-unit-tests PATCH v3 0/5] arm64: Change the default QEMU CPU type to "max" Jean-Philippe Brucker
2025-03-25 16:00 ` [kvm-unit-tests PATCH v3 1/5] configure: arm64: Don't display 'aarch64' as the default architecture Jean-Philippe Brucker
2025-03-27 17:11 ` Alexandru Elisei [this message]
2025-03-25 16:00 ` [kvm-unit-tests PATCH v3 2/5] configure: arm/arm64: Display the correct default processor Jean-Philippe Brucker
2025-03-27 17:11 ` Alexandru Elisei
2025-03-25 16:00 ` [kvm-unit-tests PATCH v3 3/5] arm64: Implement the ./configure --processor option Jean-Philippe Brucker
2025-03-25 16:00 ` [kvm-unit-tests PATCH v3 4/5] configure: Add --qemu-cpu option Jean-Philippe Brucker
2025-03-27 8:25 ` Andrew Jones
2025-03-27 17:14 ` Alexandru Elisei
2025-03-31 13:54 ` Andrew Jones
2025-03-25 16:00 ` [kvm-unit-tests PATCH v3 5/5] arm64: Use -cpu max as the default for TCG Jean-Philippe Brucker
2025-03-26 18:51 ` [kvm-unit-tests PATCH v3 0/5] arm64: Change the default QEMU CPU type to "max" Andrew Jones
2025-03-27 17:17 ` Alexandru Elisei
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=Z-WGuyzy4qxAcJD4@raptor \
--to=alexandru.elisei@arm.com \
--cc=andrew.jones@linux.dev \
--cc=eric.auger@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=vladimir.murzin@arm.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