qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Andrea Bolognani <abologna@redhat.com>, qemu-devel@nongnu.org
Cc: "Alistair Francis" <alistair23@gmail.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"David Abdurachmanov" <davidlt@rivosinc.com>
Subject: Re: [PATCH v2 2/3] binfmt: Normalize host CPU architecture
Date: Thu, 20 Feb 2025 12:05:32 +0100	[thread overview]
Message-ID: <14906c81-a057-4de4-a34b-a5ea6fb5803b@vivier.eu> (raw)
In-Reply-To: <20250127182924.103510-3-abologna@redhat.com>

Le 27/01/2025 à 19:29, Andrea Bolognani a écrit :
> Right now information regarding the family each CPU type belongs
> to is recorded in two places: the large data table at the top of
> the script, and the qemu_host_family() function.
> 
> We can make things better by mapping host CPU architecture to
> QEMU target in the few cases where the two don't already match
> and then using the data table to look up the family, same as
> we're already doing for the guest CPU architecture.
> 
> Being able to reason in terms of QEMU target regardless of
> whether we're looking at the host or guest CPU architecture will
> come in handy to implement upcoming changes.
> 
> A couple of entries are dropped in the process: BePC and Power
> Macintosh. I'm quite certain neither of those have ever been
> reported as CPU architectures by Linux. I believe many more of
> the entries that are carried forward could be dropped as well,
> but I don't have the same level of confidence there so I
> decided to play it safe just in case.
> 
> Signed-off-by: Andrea Bolognani <abologna@redhat.com>
> ---
>   scripts/qemu-binfmt-conf.sh | 44 +++++++++++++++++++++----------------
>   1 file changed, 25 insertions(+), 19 deletions(-)
> 
> diff --git a/scripts/qemu-binfmt-conf.sh b/scripts/qemu-binfmt-conf.sh
> index 426f075e31..8d9136a29f 100755
> --- a/scripts/qemu-binfmt-conf.sh
> +++ b/scripts/qemu-binfmt-conf.sh
> @@ -144,35 +144,35 @@ loongarch64_magic='\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x
>   loongarch64_mask='\xff\xff\xff\xff\xff\xff\xff\xfc\x00\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff'
>   loongarch64_family=loongarch
>   
> -qemu_get_family() {
> -    cpu=${HOST_ARCH:-$(uname -m)}
> +# Converts the name of a host CPU architecture to the corresponding QEMU
> +# target.
> +#
> +# FIXME: This can probably be simplified a lot by dropping most entries.
> +#        Remember that the script is only used on Linux, so we only need to
> +#        handle the strings Linux uses to report the host CPU architecture.
> +qemu_normalize() {
> +    cpu="$1"
>       case "$cpu" in
> -    amd64|i386|i486|i586|i686|i86pc|BePC|x86_64)
> +    i[3-6]86)
>           echo "i386"
>           ;;
> -    mips*)
> -        echo "mips"
> +    amd64)
> +        echo "x86_64"
>           ;;
> -    "Power Macintosh"|ppc64|powerpc|ppc)

I don't know why we have "Power Macintosh" as a valid value for "uname -m".
I think it's a good idea to remove it.
It's here from the beginning
08785f48b73c ("updated so that PPC/ARM/SPARC executables are automatically launched when invoked")
Perhaps it's a value coming from the OpenFirmware or MkLinux.

> +    powerpc)
>           echo "ppc"
>           ;;
> -    ppc64el|ppc64le)
> -        echo "ppcle"
> +    ppc64el)
> +        echo "ppc64le"
>           ;;
> -    arm|armel|armhf|arm64|armv[4-9]*l|aarch64)
> +    armel|armhf|armv[4-9]*l)
>           echo "arm"
>           ;;
> -    armeb|armv[4-9]*b|aarch64_be)
> +    armv[4-9]*b)
>           echo "armeb"
>           ;;
> -    sparc*)
> -        echo "sparc"
> -        ;;
> -    riscv*)
> -        echo "riscv"
> -        ;;
> -    loongarch*)
> -        echo "loongarch"
> +    arm64)
> +        echo "aarch64"
>           ;;
>       *)
>           echo "$cpu"
> @@ -309,7 +309,13 @@ EOF
>   
>   qemu_set_binfmts() {
>       # probe cpu type
> -    host_family=$(qemu_get_family)
> +    host_cpu=$(qemu_normalize ${HOST_ARCH:-$(uname -m)})
> +    host_family=$(eval echo \$${host_cpu}_family)
> +
> +    if [ "$host_family" = "" ] ; then
> +        echo "INTERNAL ERROR: unknown host cpu $host_cpu" 1>&2
> +        exit 1
> +    fi
>   
>       # register the interpreter for each cpu except for the native one
>   

Reviewed-by: Laurent Vivier <laurent@vivier.eu>


  reply	other threads:[~2025-02-20 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27 18:29 [PATCH v2 0/3] binfmt: Add --ignore-family option Andrea Bolognani
2025-01-27 18:29 ` [PATCH v2 1/3] binfmt: Shuffle things around Andrea Bolognani
2025-02-20 10:46   ` Laurent Vivier
2025-02-24  1:36   ` Alistair Francis
2025-01-27 18:29 ` [PATCH v2 2/3] binfmt: Normalize host CPU architecture Andrea Bolognani
2025-02-20 11:05   ` Laurent Vivier [this message]
2025-02-24  1:39   ` Alistair Francis
2025-02-26 21:09     ` Andrea Bolognani
2025-01-27 18:29 ` [PATCH v2 3/3] binfmt: Add --ignore-family option Andrea Bolognani
2025-02-20 11:06   ` Laurent Vivier
2025-02-28  4:24   ` Alistair Francis
2025-02-11 15:59 ` [PATCH v2 0/3] " Andrea Bolognani
2025-02-28  4:33 ` Alistair Francis

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=14906c81-a057-4de4-a34b-a5ea6fb5803b@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=abologna@redhat.com \
    --cc=alistair23@gmail.com \
    --cc=berrange@redhat.com \
    --cc=davidlt@rivosinc.com \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).