On Fri, Sep 27, 2019 at 8:30 AM Daniel P. Berrangé
<berrange(a)redhat.com> wrote:
>
> On Fri, Sep 27, 2019 at 01:26:09PM +0200, Jun Aruga wrote:
> > > Does anyone know of, or have, any critical/important use cases that would
> > be disrupted by QEMU dropping 32-bit *host* support ? If so, let me know
> > here & I can forward feedback on. Or feel free to go direct to QEMU thread
> > upstream.
> >
> > I am not a real user of ARM 32-bit. I just checked information for ARM
> > 32-bit (armv7) use cases.
> >
> > ## Raspberry Pi
> >
> > >
https://en.wikipedia.org/wiki/Raspberry_Pi
> > > The earlier V1.1 model of the Raspberry Pi 2 used a Broadcom BCM2836 SoC
with a 900 MHz 32-bit, quad-core ARM Cortex-A7 processor, with 256 KB shared L2 cache.
> > >
> > >
https://www.raspberrypi.org/blog/raspberry-pi-2-on-sale/
> >
> > It seems that the version 1.1 is the last model for 32-bit, and the
> > announcement was 5 August 2015.
> > I assume a considerable number of people using ARM 32-bit Raspberry Pi.
>
> Right, but I'm rather sceptical that people are running QEMU on the
> 32-bit RPi boards. I might be less surprised about the Linux userspace
> emulation being used, vs full VM, since the former is lower overhead.
>
>
Sorry to burst your bubble, but since the Raspberry Pi performs quite
badly as a 64-bit device for the moment, I've used it with Fedora
armv7hl instead of aarch64. I personally use the user emulation
mostly, but I know of a couple of cases where system emulation is used
(mainly for buildsys stuff).
Interesting, is there a particular reason why you run the emulation on
a Pi, as opposed to using more powerful x86 hardware for it ? I'm not
saying you're wrong todo this, just trying to understand the motivation
people have.
Regards,
Daniel
--
|: