From: Laurent Vivier <laurent@vivier.eu>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Thomas Huth" <thuth@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
BALATON Zoltan <balaton@eik.bme.hu>,
Markus Armbruster <armbru@redhat.com>,
Martin Schrodt <martin@schrodt.org>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] Drop support for 32bit hosts in qemu? (was: [PULL 1/6] audio/hda: create millisecond timers that handle IO)
Date: Wed, 27 Jun 2018 17:41:27 +0200 [thread overview]
Message-ID: <4c86fb26-f7c3-e66e-33a2-dbbfe2e70960@vivier.eu> (raw)
In-Reply-To: <db5529c6-7002-4b96-9d94-ca719e3845f8@amsat.org>
Le 27/06/2018 à 15:33, Philippe Mathieu-Daudé a écrit :
> On 06/27/2018 06:09 AM, Thomas Huth wrote:
>> On 27.06.2018 10:52, Gerd Hoffmann wrote:
>>> Hi,
>>>
>>>>> Is QEMU still useful on 32-bit hosts? Honest question!
>>>>
>>>> I guess it depends on what 32-bit hosts you consider. If you look at only
>>>> x86 vs. x86_64 then probably x86 is not that important any more but for some
>>>> embedded systems/SoCs 32bit might still be common and QEMU useful for those
>>>> (also as host not only emulated).
>>>
>>> Well. I've used kvm with an 32bit arm soc (cubietruck). It's very
>>> slow. And all the arm architecture improvements to support kvm better
>>> are for aarch64 only.
>>>
>>>> Another option might be to not support audio/hda on 32bit hosts. It's not
>>>> nice either but a lot nicer than dropping support for 32bit hosts
>>>> alltogether to fix a problem in device emulation.
>>>
>>> But it also is not useful and a waste of resources to maintain 32bit
>>> host compatibility if nobody actually uses that ...
>>>
>>> For me testbuilds are the only reason to compile qemu for 32bit hosts.
>>> Since years.
>>
>> Well, while that's true for you, me and likely most of us developers,
>> you can not know whether this is also true for all users of qemu. Thus
>> this needs to be announced first for a couple of releases so that people
>> have a chance to speak up whether they still need this or not. As
>> mentioned earlier, embedded devices are often still 32-bit and I know
>> that there really are people who use QEMU on embedded devices.
>>
>> But I think we could at least announce now already that we intend to
>> drop support for 32-bit hosts in the future (maybe not in 2 releases
>> already, but, let's say in 2020? 2020 is already the EOL of Python 2, so
>> that will rule out a bunch of other legacy hosts, too).
>
> linux-user is certainly widely used on ARMv6 / ARMv7.
>
> Known user cases:
>
> - run ARMv7 binaries on ARMv6
> - run armhf binaries on armel
> - run x86-64 binaries on ARMv7
>
I run i386 binaries on ARMv6.
I use it to run i386 printer driver on my raspberry Pi B+.
Brother doesn't provide the binary for ARM, neither the source.
Thanks,
Laurent
next prev parent reply other threads:[~2018-06-27 15:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 13:12 [Qemu-devel] [PULL 0/6] Audio 20180625 patches Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 1/6] audio/hda: create millisecond timers that handle IO Gerd Hoffmann
2018-06-26 19:55 ` Max Reitz
2018-06-27 6:51 ` Gerd Hoffmann
2018-06-27 7:24 ` Thomas Huth
2018-06-27 7:57 ` [Qemu-devel] Drop support for 32bit hosts in qemu? (was: [PULL 1/6] audio/hda: create millisecond timers that handle IO) Markus Armbruster
2018-06-27 8:09 ` [Qemu-devel] Drop support for 32bit hosts in qemu? Thomas Huth
2018-06-27 8:56 ` Gerd Hoffmann
2018-06-27 11:08 ` Alex Bennée
2018-06-27 11:09 ` Thomas Huth
2018-06-27 8:15 ` [Qemu-devel] Drop support for 32bit hosts in qemu? (was: [PULL 1/6] audio/hda: create millisecond timers that handle IO) BALATON Zoltan
2018-06-27 8:52 ` Gerd Hoffmann
2018-06-27 9:09 ` Thomas Huth
2018-06-27 13:33 ` Philippe Mathieu-Daudé
2018-06-27 15:41 ` Laurent Vivier [this message]
2018-06-27 18:44 ` Dr. David Alan Gilbert
2018-06-27 19:55 ` Laurent Vivier
2018-06-27 10:49 ` Peter Maydell
2018-06-27 11:09 ` Dr. David Alan Gilbert
2018-06-27 13:08 ` Alex Bennée
2018-06-27 13:09 ` Alex Bennée
2018-06-27 11:09 ` Daniel P. Berrangé
2018-06-27 13:03 ` Alex Bennée
2018-06-27 13:38 ` Philippe Mathieu-Daudé
2018-06-27 13:02 ` [Qemu-devel] Drop support for 32bit hosts in qemu? Juan Quintela
2018-06-27 13:11 ` Daniel P. Berrangé
2018-06-27 11:13 ` [Qemu-devel] [PULL 1/6] audio/hda: create millisecond timers that handle IO Gerd Hoffmann
2018-06-27 13:15 ` Paolo Bonzini
2018-06-27 12:21 ` Eric Blake
2018-06-29 8:19 ` Peter Maydell
2018-06-29 15:11 ` Eric Blake
2018-06-25 13:12 ` [Qemu-devel] [PULL 2/6] audio/hda: turn some dprintfs into trace points Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 3/6] audio/hda: tweak timer adjust logic Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 4/6] audio/hda: detect output buffer overruns Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 5/6] audio/hda: enable new timer code by default Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 6/6] audio: Convert use of atoi to qemu_strtoi Gerd Hoffmann
2018-06-25 15:37 ` [Qemu-devel] [PULL 0/6] Audio 20180625 patches Peter Maydell
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=4c86fb26-f7c3-e66e-33a2-dbbfe2e70960@vivier.eu \
--to=laurent@vivier.eu \
--cc=armbru@redhat.com \
--cc=aurelien@aurel32.net \
--cc=balaton@eik.bme.hu \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=martin@schrodt.org \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).