qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, stefanha@redhat.com,
	mark.cave-ayland@ilande.co.uk, "Liviu Ionescu" <ilg@livius.net>
Subject: Re: [PATCH 0/1] meson: Deprecate 32-bit host systems
Date: Fri, 31 Jan 2025 08:46:32 -0800	[thread overview]
Message-ID: <62449bfd-eb65-41d6-ae53-0333bcb603b3@linaro.org> (raw)
In-Reply-To: <8a54600c-ff3f-42dd-b164-62a57de867df@redhat.com>

On 1/29/25 04:47, Paolo Bonzini wrote:
> The difference with TCG of course is that TCG is in active development, and therefore its 
> 32-bit host support is not surviving passively in the same way that a random device is.  
> Still, I think we can identify at least three different parts that should be treated 
> differently: 64-on-32, 32-on-32 system-mode emulation and 32-on-32 user-mode emulation.

Why the user/system split for 32-on-32?

> We could and should remove 64-on-32, maybe even without a deprecation period, but the rest 
> I'm not so sure.  I don't know enough to understand their maintenance cost (other than the 
> mere existence of the 32-bit TCG backends), but it's certainly not comparable to 64-on-32.

Ok, lemme see how easy it is to prohibit configuring 64-on-32.

But I also think we should still deprecate 32-bit hosts, sooner rather than later.  Even 
if we have no immediate plans to remove them.  I think we want interested parties to speak 
up.  At some point this decade I want to be able to say: we've given you fair warning and 
time is up.


r~


  reply	other threads:[~2025-01-31 16:47 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 ` [PATCH 0/1] meson: Deprecate 32-bit host systems Thomas Huth
2025-01-28  9:02   ` 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 [this message]
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=62449bfd-eb65-41d6-ae53-0333bcb603b3@linaro.org \
    --to=richard.henderson@linaro.org \
    --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=stefanha@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 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).