qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: 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>,
	"Richard Henderson" <richard.henderson@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: Wed, 29 Jan 2025 13:47:31 +0100	[thread overview]
Message-ID: <8a54600c-ff3f-42dd-b164-62a57de867df@redhat.com> (raw)
In-Reply-To: <CAFEAcA_CfVfypS5yUtT3V34CDxmAqx7wYnDoKPfHq-o=54GgAg@mail.gmail.com>

On 1/29/25 13:23, Peter Maydell wrote:
> I'm not really strongly opposed to dropping 32-bit host support,
> but I don't think a thread on qemu-devel is exactly likely to
> get the attention of the people who might be using this
> functionality. (You could argue that functionality without
> representation among the developer community is fair game
> for being dumped even if it has users, of course.)
On the other hand, broken tests that no one even runs among the 
developers are not particularly significant.  It's not surprising that 
tests do not pass the first time and need a little tweaking when trying 
them on a new platform.

There are many examples of parts of QEMU that stayed unmaintained for 
years, working relatively well for limited use cases, and were only 
later revamped.  Most of those that I can remember are guest side: the 
TCG frontend for x86, ESP emulation in hw/scsi, VGA.  In fact VGA still 
has a good number of emulation deficiencies and it's deprecated for 
virtualization use, but no one in their right mind would suggest slating 
it for removal.

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.

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.

Paolo



  reply	other threads:[~2025-01-29 12:48 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 [this message]
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=8a54600c-ff3f-42dd-b164-62a57de867df@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=ilg@livius.net \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).