From: Thomas Huth <thuth@redhat.com>
To: Andrew Randrianasulu <randrianasulu@gmail.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-discuss@nongnu.org,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: dropping 32-bit host support
Date: Thu, 16 Mar 2023 12:02:33 +0100 [thread overview]
Message-ID: <ac632c34-42e0-d715-52d9-b70ead6296a7@redhat.com> (raw)
In-Reply-To: <CA+rFky4su7ZEo8pNQGk3qEkTOLEkFAqO2Tsrh6VyDaNOf7w=_Q@mail.gmail.com>
On 16/03/2023 11.22, Andrew Randrianasulu wrote:
>
>
> чт, 16 мар. 2023 г., 12:17 Andrew Randrianasulu <randrianasulu@gmail.com
> <mailto:randrianasulu@gmail.com>>:
>
>
>
> чт, 16 мар. 2023 г., 11:31 Thomas Huth <thuth@redhat.com
> <mailto:thuth@redhat.com>>:
>
> On 16/03/2023 08.36, Philippe Mathieu-Daudé wrote:
> > On 16/3/23 08:17, Andrew Randrianasulu wrote:
> >>
> >> чт, 16 мар. 2023 г., 10:05 Philippe Mathieu-Daudé
> <philmd@linaro.org <mailto:philmd@linaro.org>
> >> <mailto:philmd@linaro.org <mailto:philmd@linaro.org>>>:
> >>
> >> Hi Andrew,
> >>
> >> On 16/3/23 01:57, Andrew Randrianasulu wrote:
> >> > Looking at https://wiki.qemu.org/ChangeLog/8.0
> <https://wiki.qemu.org/ChangeLog/8.0>
> >> <https://wiki.qemu.org/ChangeLog/8.0
> <https://wiki.qemu.org/ChangeLog/8.0>>
> >> > <https://wiki.qemu.org/ChangeLog/8.0
> <https://wiki.qemu.org/ChangeLog/8.0>
> >> <https://wiki.qemu.org/ChangeLog/8.0
> <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)
>
> All current PCs have multiple gigabytes of RAM, so using a 32-bit
> userspace
> to save some few bytes sounds weird.
>
>
> I think difference more like in 20-30% (on disk and in ram), not *few
> bytes*.
>
>
> I stand (self) corrected on *on disk* binary size, this parameter tend to be
> ~same between bash / php binaries from Slackware 15.0 i586/x86_64. I do not
> have full identical x64 Slackware setup for measuring memory impact.
>
>
> Still, pushing users into endless hw upgrade is no fun:
>
> https://hackaday.com/2023/02/28/repurposing-old-smartphones-when-reusing-makes-more-sense-than-recycling/ >
>
> note e-waste and energy consumption
Now you're mixing things quite badly. That would be an argument in the years
before 2010 maybe, when not everybody had a 64-bit processor in their PC
yet, but it's been now more than 12 years that all recent Desktop processors
feature 64-bit mode. So if QEMU stops supporting 32-bit x86 environments,
this is not forcing you to buy a new hardware, since you're having a 64-bit
hardware already anyway. If someone still has plain 32-bit x86 hardware
around for their daily use, that's certainly not a piece of hardware you
want to run QEMU on, since it's older than 12 years already, and thus not
really strong enough to run a recent emulator in a recent way.
Thomas
next prev parent reply other threads:[~2023-03-16 11:04 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 [this message]
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é
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=ac632c34-42e0-d715-52d9-b70ead6296a7@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=randrianasulu@gmail.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).