qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	libvir-list@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Reinoud Zandijk" <reinoud@netbsd.org>,
	"Ryo ONODERA" <ryoon@netbsd.org>,
	"Brad Smith" <brad@comstyle.com>, "Stefan Weil" <sw@weilnetz.de>
Subject: Re: [RFC PATCH] docs/about/deprecated: Deprecate 32-bit host systems
Date: Mon, 30 Jan 2023 13:22:22 +0100	[thread overview]
Message-ID: <f94ce115-b962-b19d-269e-4f593da61c6f@redhat.com> (raw)
In-Reply-To: <Y9exrDWT2NUoinu1@redhat.com>

On 30/01/2023 13.01, Daniel P. Berrangé wrote:
> On Mon, Jan 30, 2023 at 11:47:02AM +0000, Peter Maydell wrote:
>> On Mon, 30 Jan 2023 at 11:44, Thomas Huth <thuth@redhat.com> wrote:
>>>
>>> Testing 32-bit host OS support takes a lot of precious time during the QEMU
>>> contiguous integration tests, and considering that many OS vendors stopped
>>> shipping 32-bit variants of their OS distributions and most hardware from
>>> the past >10 years is capable of 64-bit
>>
>> True for x86, not necessarily true for other architectures.
>> Are you proposing to deprecate x86 32-bit, or all 32-bit?
>> I'm not entirely sure about whether we're yet at a point where
>> I'd want to deprecate-and-drop 32-bit arm host support.

Even mobile phones have 64-bit processors nowadays, Rasberry PIs are 64-bit 
nowadays ... which arm hosts scenarios are still limited to 32-bit ?

Also, as far as I know, 32-bit KVM arm support has been removed from the 
Linux kernel a while ago already, so it's just about TCG now ... is there 
really still that much interest in running emulation on a non-beefy 32-bit host?

Anyway, we could add the deprecation notice now to find out if there are 
still 32-bit users out there who will then start complaining about this.

> Do we have a feeling on which aspects of 32-bit cause us the support
> burden ? The boring stuff like compiler errors from mismatched integer
> sizes is mostly quick & easy to detect simply through a cross compile.

The burden are the CI minutes of the shared CI runners. We've got quite a 
bunch of 32-bit jobs in the CI:

- cross-armel-system
- cross-armel-user
- cross-armhf-system
- cross-armhf-user
- cross-i386-system
- cross-i386-user
- cross-i386-tci
- cross-mipsel-system
- cross-mipsel-user
- cross-win32-system

If we could finally drop supporting 32-bit hosts, that would help with our 
CI minutes problem quite a lot, I think.

  Thomas



  reply	other threads:[~2023-01-30 12:23 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 11:44 [RFC PATCH] docs/about/deprecated: Deprecate 32-bit host systems Thomas Huth
2023-01-30 11:47 ` Peter Maydell
2023-01-30 12:01   ` Daniel P. Berrangé
2023-01-30 12:22     ` Thomas Huth [this message]
2023-01-30 12:43       ` Daniel P. Berrangé
2023-01-30 13:07         ` Thomas Huth
2023-01-30 19:19     ` Richard Henderson
2023-01-30 23:14       ` Philippe Mathieu-Daudé
2023-01-30 23:33         ` Richard Henderson
2023-01-31  0:19           ` Philippe Mathieu-Daudé
2023-01-30 20:45     ` Alex Bennée
2023-02-05 22:12       ` Mark Cave-Ayland
2023-04-04 14:00         ` Thomas Huth
2023-04-04 14:20           ` Cédric Le Goater
2023-04-04 15:58             ` BALATON Zoltan
2023-04-04 14:32           ` Cédric Le Goater
2023-04-04 15:42             ` BALATON Zoltan
2023-04-05  8:01               ` Thomas Huth
2023-04-05 11:54                 ` BALATON Zoltan
2023-04-05 12:51                   ` Thomas Huth
2023-04-04 15:50           ` BALATON Zoltan
2023-04-05 21:01           ` Mark Cave-Ayland
2023-02-22  9:11       ` Bernhard Beschow
2023-02-22  9:51         ` Daniel P. Berrangé
2023-02-22 12:28           ` Reinoud Zandijk
2023-02-22 13:37             ` Alex Bennée
2023-02-17 10:36 ` Markus Armbruster
2023-02-17 10:40   ` Daniel P. Berrangé
2023-02-17 10:45   ` Claudio Fontana
2023-02-17 10:47   ` Daniel P. Berrangé
2023-02-17 11:05     ` Stefan Weil via
2023-02-17 11:43       ` Markus Armbruster
2023-02-17 11:47       ` Daniel P. Berrangé
2023-02-19 11:27       ` Reinoud Zandijk
2023-02-19 12:12         ` Stefan Weil via
2023-02-17 16:38     ` Paolo Bonzini
2023-02-17 17:43       ` Philippe Mathieu-Daudé
2023-02-17 18:57         ` Thomas Huth
2023-02-18 22:54           ` Jiaxun Yang
2023-02-17 19:49       ` Thomas Huth
2023-02-17 16:06   ` Reinoud Zandijk
2023-02-17 17:20     ` Daniel P. Berrangé
2023-02-17 18:22     ` Richard Henderson
2023-02-19 11:07       ` Reinoud Zandijk
2023-02-17 11:09 ` Claudio Fontana

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=f94ce115-b962-b19d-269e-4f593da61c6f@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=brad@comstyle.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=reinoud@netbsd.org \
    --cc=richard.henderson@linaro.org \
    --cc=ryoon@netbsd.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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).