From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, stefanha@redhat.com,
pbonzini@redhat.com, berrange@redhat.com, philmd@linaro.org,
mark.cave-ayland@ilande.co.uk, alex.bennee@linaro.org,
Liviu Ionescu <ilg@livius.net>
Subject: Re: [PATCH 0/1] meson: Deprecate 32-bit host systems
Date: Tue, 28 Jan 2025 05:00:35 +0100 [thread overview]
Message-ID: <9a280789-9248-4eca-b50c-048fc58e3f53@redhat.com> (raw)
In-Reply-To: <20250128004254.33442-1-richard.henderson@linaro.org>
On 28/01/2025 01.42, Richard Henderson wrote:
> Time for our biennial attempt to kill ancient hosts.
>
> I've been re-working the tcg code generator a bit over the holidays.
> One place that screams for a bit of cleanup is with 64-bit guest
> addresses on 32-bit hosts. Of course the best "cleanup" is to not
> have to handle such silliness at all.
>
> Two years after Thomas' last attempt,
>
> https://lore.kernel.org/qemu-devel/20230130114428.1297295-1-thuth@redhat.com/
>
> which resulted only in deprecation of i686 host for system emulation.
> By itself, this just isn't enough for large-scale cleanups.
>
> I'll note that we've separately deprecated mips32, set to expire
> with the end of Debian bookworm, set to enter LTS in June 2026.
>
> I'll note that there is *already* no Debian support for ppc32,
> and that I am currently unable to cross-compile that host at all.
IIRC the biggest pushback that I got two years ago was with regards to
32-bit arm: The recommended version of Raspberry Pi OS is still 32-bit:
https://lore.kernel.org/qemu-devel/F852C238-77B8-4E24-9494-8D060EB78F9F@livius.net/
And looking at https://www.raspberrypi.com/software/operating-systems/ this
still seems to be the case...
So I guess the main question is now: Would it be ok to kill support for
32-bit Raspberry Pi OS nowadays?
> Showing my hand a bit, I am willing to limit deprecation to
> 64-bit guests on 32-bit hosts. But I'd prefer to go the whole hog:
> unconditional support for TCG_TYPE_I64 would remove a *lot* of
> 32-bit fallback code.
Sound like a good alternative to me!
Thomas
next prev parent reply other threads:[~2025-01-28 4:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 0:42 [PATCH 0/1] meson: Deprecate 32-bit host systems Richard Henderson
2025-01-28 0:42 ` [PATCH 1/1] meson: Deprecate 32-bit host support Richard Henderson
2025-01-28 4:00 ` Thomas Huth [this message]
2025-01-28 9:02 ` [PATCH 0/1] meson: Deprecate 32-bit host systems Alex Bennée
2025-01-28 9:16 ` Daniel P. Berrangé
2025-01-28 9:17 ` Philippe Mathieu-Daudé
2025-01-28 9:27 ` Daniel P. Berrangé
2025-01-28 10:01 ` Philippe Mathieu-Daudé
2025-01-28 10:02 ` Philippe Mathieu-Daudé
2025-01-29 6:23 ` Thomas Huth
2025-01-29 12:23 ` Peter Maydell
2025-01-29 12:47 ` Paolo Bonzini
2025-01-31 16:46 ` Richard Henderson
2025-01-31 17:08 ` Paolo Bonzini
2025-01-31 21:28 ` Daniel P. Berrangé
2025-02-03 9:10 ` Alex Bennée
2025-02-03 16:06 ` Philippe Mathieu-Daudé
2025-01-28 20:39 ` Richard Henderson
2025-02-01 15:20 ` James Cloos
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=9a280789-9248-4eca-b50c-048fc58e3f53@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=ilg@livius.net \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@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 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).