qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Liviu Ionescu" <ilg@livius.net>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Andrew Randrianasulu <randrianasulu@gmail.com>,
	qemu-discuss@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: dropping 32-bit host support
Date: Thu, 16 Mar 2023 09:36:22 +0100	[thread overview]
Message-ID: <5fbcb311-228f-2590-e5c5-21e7f043c1cf@redhat.com> (raw)
In-Reply-To: <F852C238-77B8-4E24-9494-8D060EB78F9F@livius.net>

On 16/03/2023 09.07, Liviu Ionescu wrote:
> 
> 
>> On 16 Mar 2023, at 09:57, Liviu Ionescu <ilg@livius.net> wrote:
>>
>> I'm not targeting RPi2; there are a lot of RPi4 with less than 8GB RAM (most of them, actually), and even more RPi3, with even less RAM), and people prefer to continue using the 32-bit OS on them, which works quite fine;
> 
> Like it or not, as long as Raspberry does not explicitly deprecate the 32-bit OS, people will continue to use it, and for good reasons.
> 
> As of now, it is even 'Our recommended operating system for most users.':

I'd say "most users" != "the people who want to run QEMU here". If you 
really really want to run QEMU on such a system, you can also install a 
64-bit OS there.

Please also consider that we're only talking about marking the 32-bit arm 
hosts as deprecated in our docs right now. It will take another year (or 
maybe more) until the deprecation will turn into a real unsupported state. I 
assume by that point in time, more and more RPi users will have switched to 
a 64-bit OS instead.

  Thomas



  reply	other threads:[~2023-03-16  8:37 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é
2023-03-16  7:57     ` Liviu Ionescu
2023-03-16  8:07       ` Liviu Ionescu
2023-03-16  8:36         ` Thomas Huth [this message]
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=5fbcb311-228f-2590-e5c5-21e7f043c1cf@redhat.com \
    --to=thuth@redhat.com \
    --cc=ilg@livius.net \
    --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).