qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Liviu Ionescu <ilg@livius.net>,
	Andrew Randrianasulu <randrianasulu@gmail.com>
Cc: qemu-discuss@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>,
	Thomas Huth <thuth@redhat.com>
Subject: Re: dropping 32-bit host support
Date: Thu, 16 Mar 2023 08:29:02 +0100	[thread overview]
Message-ID: <35022ff8-bf4b-1f52-73f9-db25c776cec1@linaro.org> (raw)
In-Reply-To: <3DD8295F-4BE0-4262-8C68-4A85A56D63C7@livius.net>

Hi Liviu,

On 16/3/23 07:19, Liviu Ionescu wrote:
> 
> 
>> On 16 Mar 2023, at 02:57, Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
>>
>> Looking at https://wiki.qemu.org/ChangeLog/8.0
>>
>> ===
>> System emulation on 32-bit x86 and ARM hosts has been deprecated. The QEMU project no longer considers 32-bit x86 and ARM support for system emulation to be an effective use of its limited resources, and thus intends to discontinue.
>>
>>   ==
>>
>> well, I guess arguing from memory-consuption point on 32 bit x86 hosts (like my machine where I run 32 bit userspace on 64 bit kernel) is not going anywhere, but what about 32bit userspace on Android tablets, either via Limbo emulator or qemu itself in Termux?
> 
> or the countless 32-bit Raspberry Pi?
> 
> my xPack binary tools, which include qemu arm & qemu riscv, are also available for arm 32-bit, and the analytics show about the same number of downloads for 32-bit as for 64-bit.
> 
> given the current chip shortages, I estimate that the 32-bit Arm binaries will still be useful for a few more years.

IIUC xPack uses npm -- so work on any environment where npm works --,
and fetch/install existing toolchains. Looking at ARM, all offered
toolchains are 64-bit host [1] and the deprecated [2]. Toolchains for
32-bit hosts are still available but also listed as "deprecated" [3].

[1] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads
[2] https://developer.arm.com/downloads/-/gnu-a
[3] https://developer.arm.com/downloads/-/gnu-rm

If QEMU is useful to you for testing installing xPack on a 32-bit
emulated guest, I strongly recommend you to do that on a 64-bit host
rather than a limited performance 32-bit Raspberry Pi 2, it is a much
more pleasant "user experience". IMHO Raspberry Pi 2 was designed for
embedded setup and prototyping with other electronic devices, not
really as a compute intensive build CPU.

>> At least I hope it will be not *actively* (intentionally) broken, just ...unsupported (so users who know how to run git revert still will get their build for some more time).
> 
> I concur, please do not intentionally break support for arm 32-bit, this will make a lot of unhappy users, who currently have no choice to upgrade.
> 
> 
> thank you,
> 
> Liviu

Regards,

Phil.



  parent reply	other threads:[~2023-03-16  7:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+rFky6A9Q_5sJ4WDO-Z2HBT59qiNgr8A-xk+O7-gnAMZmHt2A@mail.gmail.com>
2023-03-16  7:05 ` dropping 32-bit host support Philippe Mathieu-Daudé
2023-03-16  7:17   ` Andrew Randrianasulu
2023-03-16  7:36     ` Philippe Mathieu-Daudé
2023-03-16  7:44       ` Andrew Randrianasulu
2023-03-16  8:31       ` Thomas Huth
2023-03-16  9:17         ` Andrew Randrianasulu
2023-03-16 10:22           ` Andrew Randrianasulu
2023-03-16 10:56             ` Philippe Mathieu-Daudé
2023-03-16 11:04               ` Andrew Randrianasulu
2023-03-16 11:15                 ` Thomas Huth
2023-03-16 11:02             ` Thomas Huth
2023-03-16 11:11               ` Andrew Randrianasulu
2023-03-16 12:35                 ` Daniel P. Berrangé
2023-03-16 13:01                   ` Andrew Randrianasulu
2023-03-16 13:32                     ` Thomas Huth
2023-03-16 15:21                       ` Warner Losh
2023-03-16 15:29                         ` Andrew Randrianasulu
2023-03-16 15:27                       ` Andrew Randrianasulu
2023-03-16 15:39                     ` Daniel P. Berrangé
2023-03-17  8:03                   ` Andrew Randrianasulu
2023-03-16 10:00         ` Markus Armbruster
2023-03-16 10:05           ` Andrew Randrianasulu
     [not found] ` <3DD8295F-4BE0-4262-8C68-4A85A56D63C7@livius.net>
2023-03-16  7:29   ` Philippe Mathieu-Daudé [this message]
2023-03-16  7:57     ` Liviu Ionescu
2023-03-16  8:07       ` Liviu Ionescu
2023-03-16  8:36         ` Thomas Huth
2023-03-16  8:42           ` Liviu Ionescu

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=35022ff8-bf4b-1f52-73f9-db25c776cec1@linaro.org \
    --to=philmd@linaro.org \
    --cc=ilg@livius.net \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=randrianasulu@gmail.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).