All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"open list:Block layer core" <qemu-block@nongnu.org>,
	qemu-s390x <qemu-s390x@nongnu.org>
Subject: Re: [RFC PATCH] buildsys: Stop checking for ESA/390 host
Date: Wed, 20 May 2026 11:34:02 +0200	[thread overview]
Message-ID: <87h5o2o25x.fsf@redhat.com> (raw)
In-Reply-To: <CABgObfYh0k=Cp-1zfg-EDSMRobbDkW0OpR1QD1tGAYmHDSuorw@mail.gmail.com>

On Tue, May 19 2026, Paolo Bonzini <pbonzini@redhat.com> wrote:

> Il mar 19 mag 2026, 16:59 Philippe Mathieu-Daudé <philmd@linaro.org> ha
> scritto:
>
>> We still build QEMU tools on 32-bit hosts (see commit
>> cf634dfcd8f), however no OS supported by QEMU still runs
>> on ESA/390 (Linux dropped support in release 4.1 in 2015).
>>
>
> If Linux still supports 31-bit *userspace binaries*, I would keep the
> configure check, so that 32-bit s390 is properly detected as an unsupported
> CPU:

FWIW, Linux removed support for the 31 bit compat code in v6.19 (late
last year); it is unclear if anyone had been using it recently anyway.

>
> elif check_define __s390__ ; then
>>   if check_define __s390x__ ; then
>>     cpu="s390x"
>>   else
>>     cpu="s390"
>>   fi
>>
>
> and perhaps keep the CPU_CFLAGS only from the other hunk:
>
>   s390)
>>     linux_arch=s390
>>     CPU_CFLAGS="-m31"
>>     ;;
>>
>
>    s390x)
>>      host_arch=s390x
>>      linux_arch=s390
>>

I'm also wondering if anyone had actually tried to use QEMU on such a
setup recently; I don't have a setup to test that in any case.



      reply	other threads:[~2026-05-20 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 14:58 [RFC PATCH] buildsys: Stop checking for ESA/390 host Philippe Mathieu-Daudé
2026-05-19 15:04 ` Peter Maydell
2026-05-19 15:32 ` Paolo Bonzini
2026-05-20  9:34   ` Cornelia Huck [this message]

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=87h5o2o25x.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.