All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Janosch Frank" <frankja@linux.ibm.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: Compiling the s390-ccw bios with clang (was: Re: s390-ccw: warning: writing 1 byte into a region of size 0)
Date: Fri, 23 Apr 2021 10:00:34 +0100	[thread overview]
Message-ID: <YIKMsoAOrBYO7K7Y@redhat.com> (raw)
In-Reply-To: <44304a9e-9907-31ec-53a2-44bc7123c688@redhat.com>

On Fri, Apr 23, 2021 at 10:52:35AM +0200, Thomas Huth wrote:
> On 23/04/2021 10.47, Daniel P. Berrangé wrote:
> > On Fri, Apr 23, 2021 at 10:22:28AM +0200, Thomas Huth wrote:
> > > On 23/04/2021 10.07, Cornelia Huck wrote:
> > > > On Fri, 23 Apr 2021 09:57:08 +0200
> > > > Thomas Huth <thuth@redhat.com> wrote:
> > > > 
> > > > > On 23/04/2021 08.52, Christian Borntraeger wrote:
> > > > > [...]
> > > > > > We can of course discuss if we compile the BIOS for z10 instead of z900. TCG
> > > > > > in the mean time can handle up to z13 and z10 is now also 13 years old.
> > > > > 
> > > > > I'd really like to see us supporting Clang in the s390-ccw bios, too, since
> > > > > it provides additional useful compiler warnings ... but switching the -mz900
> > > > > to -mz10 here also means that we could not boot VMs anymore that use a CPU
> > > > > that is older than the z10...
> > > > 
> > > > We could still boot a kernel/initrd directly, couldn't we?
> > > 
> > > Yes, but that will certainly require some documentation effort to make it
> > > clear to the users that they need to use "-kernel" in case they want to run
> > > an older guest...
> > > 
> > > > > Is anybody still using such old CPUs? Should we maybe deprecate all CPUs
> > > > > that are older than the z10 in QEMU? Alternatively, we could try to detect
> > > > > Clang in the Makefile, and only use -mz10 in that case and continue to use
> > > > > -mz900 in the other case...?
> > > > 
> > > > So, the issue with clang is that it compiles to at least a z10, right?
> > > 
> > > Right, Clang does not support anything that is older than a z10.
> > 
> > IIUC, according to wikipedia
> > 
> >     - z10 series was introduced in 2008
> >     - z900 series was introduced in 2000
> > 
> > Even the z10 is well older than the oldest OS platform we support.
> > 
> > Though I presume people keep mainframes deployed for longer than commodity
> > x86 hardware, it doesn't seem too unreasonable to say z10 is the oldest
> > we'll support.
>
> Well, we're talking about *guest* support here. So with that argumentation,
> we could also remove support for old CPUs like "486" or "SandyBridge" from
> qemu-system-x86_64 ... should we maybe also start the deprecation there?

Oh true, I forgot it would have implications for usability of the -cpu
flag choices, I was only thinking about the guest OS, as you can sitll
use a guest OS compiled for z900 even if the BIOS is targetting z10.

So need to compile BIOS with z900 is effectively equivalent to the need
to compile x86 BIOS for oldest generation CPU.

Downstream distros have the choice to limit what CPUs they wish to
support, but upstream if QEMU targets legacy emulation use cases, then
we want to support all CPUs.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-04-23  9:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  4:18 s390-ccw: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] Philippe Mathieu-Daudé
2021-04-22  4:47 ` Thomas Huth
2021-04-22  6:04   ` Christian Borntraeger
2021-04-22 10:15   ` Daniel P. Berrangé
2021-04-22 10:30     ` Peter Maydell
2021-04-22 11:24       ` Philippe Mathieu-Daudé
2021-04-22 11:47         ` Thomas Huth
2021-04-22 12:41           ` Christian Borntraeger
2021-04-22 14:31             ` Philippe Mathieu-Daudé
2021-04-22 15:38               ` Thomas Huth
2021-04-22 15:43                 ` Philippe Mathieu-Daudé
2021-04-22 15:52                 ` Stefano Garzarella
2021-04-22 16:07                   ` Thomas Huth
2021-04-22 16:54                     ` Philippe Mathieu-Daudé
2021-04-23  6:40                       ` Stefano Garzarella
2021-04-23  6:52                         ` Christian Borntraeger
2021-04-23  7:57                           ` Compiling the s390-ccw bios with clang (was: Re: s390-ccw: warning: writing 1 byte into a region of size 0) Thomas Huth
2021-04-23  8:05                             ` Compiling the s390-ccw bios with clang Christian Borntraeger
2021-04-23  8:07                             ` Compiling the s390-ccw bios with clang (was: Re: s390-ccw: warning: writing 1 byte into a region of size 0) Cornelia Huck
2021-04-23  8:22                               ` Thomas Huth
2021-04-23  8:47                                 ` Daniel P. Berrangé
2021-04-23  8:52                                   ` Thomas Huth
2021-04-23  9:00                                     ` Daniel P. Berrangé [this message]
2021-04-22 11:48         ` s390-ccw: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] Daniel P. Berrangé
2021-04-22 14:34           ` Philippe Mathieu-Daudé

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=YIKMsoAOrBYO7K7Y@redhat.com \
    --to=berrange@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sgarzare@redhat.com \
    --cc=thuth@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 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.