qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	libvir-list@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	Reinoud Zandijk <reinoud@netbsd.org>,
	Ryo ONODERA <ryoon@netbsd.org>, Brad Smith <brad@comstyle.com>,
	Stefan Weil <sw@weilnetz.de>, Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [RFC PATCH] docs/about/deprecated: Deprecate 32-bit host systems
Date: Mon, 30 Jan 2023 13:33:36 -1000	[thread overview]
Message-ID: <8a802013-1bdf-8b56-d74c-0e3ee1c203ae@linaro.org> (raw)
In-Reply-To: <51e135e0-0c94-43d6-c408-1a9d556e9e42@linaro.org>

On 1/30/23 13:14, Philippe Mathieu-Daudé wrote:
> On 30/1/23 20:19, Richard Henderson wrote:
> 
>> But I do question whether we need to support 64-bit guests on 32-bit hosts at all.
>> Retaining 32-bit on 32-bit allows arm32 to emulate i686, which I suspect, but have no 
>> proof, is the limit of what users actually want.
> 
> I presume you implicitly restrict that to user emulation, right?

No, there's no specific reason to eliminate e.g. qemu-system-i386. or any other 32-bit 
guest.  Though quite often such hardware doesn't really have enough ram to do a good job, 
that's not a technical argument against.


> WRT i686, if your example is "i686 useremu on non-x86 embedde router"
> then any 32-bit host is potentially interested, not only arm32.

arm32 was merely an example -- the other 32-bit hosts are i686, mips, ppc.  But we don't 
have many of them.

> I remember being able to run armhf binaries on armel hosts (and vice
> versa) was useful 7 years ago.

Fair enough.

> Today I have no clue, we could poll the community and some 
> distributions.

Sure.


r~


  reply	other threads:[~2023-01-30 23:34 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
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 [this message]
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=8a802013-1bdf-8b56-d74c-0e3ee1c203ae@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=berrange@redhat.com \
    --cc=brad@comstyle.com \
    --cc=libvir-list@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=reinoud@netbsd.org \
    --cc=ryoon@netbsd.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    --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).