qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v3 3/4] target-ppc: ppc can be either endian


From: Alexander Graf
Subject: Re: [Qemu-devel] [PATCH v3 3/4] target-ppc: ppc can be either endian
Date: Wed, 07 May 2014 11:09:56 +0200
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0


On 07.05.14 10:14, Greg Kurz wrote:
On Tue, 6 May 2014 19:37:22 +0100
Peter Maydell <address@hidden> wrote:
On 5 May 2014 09:07, Greg Kurz <address@hidden> wrote:
POWER7, POWER7+ and POWER8 families use the ILE bit of the LPCR
special purpose register to decide the endianness to use when
entering interrupt handlers. When running a Linux guest, this
provides a hint on the endianness used by the kernel. From a
QEMU point of view, the information is needed for legacy virtio
support and crash dump support as well.
Do you care about the case of:
  * kernel bigendian
Yes. FWIW, ppc64 is still widely used in big endian mode we don't
want to break.

  * userspace littleendian (or vice-versa)
We don't care about userspace here. We assume that virtio structures are
owned by the guest kernel.

  * guest kernel passes virtio device through to guest userspace
Not sure to understand... could you please point me to an example ?

  * guest userspace is doing the manipulation of the device

Hmm... you mean we would have virtio drivers implemented in the guest
userspace ? Does that exist ? Please elaborate.

Virtio bypasses the IOMMU by design, so user space drivers don't make sense here :).

I don't think we should overengineer hacks for legacy virtio.


Alex




reply via email to

[Prev in Thread] Current Thread [Next in Thread]