From: Alexander Graf <agraf@suse.de>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: bharata@linux.vnet.ibm.com,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 3/4] target-ppc: ppc can be either endian
Date: Wed, 07 May 2014 11:09:56 +0200 [thread overview]
Message-ID: <5369F864.7040406@suse.de> (raw)
In-Reply-To: <20140507101443.146fc26d@bahia.local>
On 07.05.14 10:14, Greg Kurz wrote:
> On Tue, 6 May 2014 19:37:22 +0100
> Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 5 May 2014 09:07, Greg Kurz <gkurz@linux.vnet.ibm.com> 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
next prev parent reply other threads:[~2014-05-07 9:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 8:02 [Qemu-devel] [PATCH v3 0/4] little-endian dump for ppc64 Greg Kurz
2014-05-05 8:04 ` [Qemu-devel] [PATCH v3 1/4] dump: Make DumpState and endian conversion routines available for arch-specific dump code Greg Kurz
2014-05-05 8:05 ` [Qemu-devel] [PATCH v3 2/4] ppc64-dump: Support dump for little endian ppc64 Greg Kurz
2014-05-05 11:04 ` Alexander Graf
2014-05-07 8:20 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2014-05-07 19:02 ` Tom Musta
2014-05-07 20:54 ` Tom Musta
2014-05-07 20:59 ` Alexander Graf
2014-05-08 7:49 ` Greg Kurz
2014-05-05 8:07 ` [Qemu-devel] [PATCH v3 3/4] target-ppc: ppc can be either endian Greg Kurz
2014-05-06 18:37 ` Peter Maydell
2014-05-07 8:14 ` Greg Kurz
2014-05-07 9:06 ` Peter Maydell
2014-05-07 9:09 ` Alexander Graf [this message]
2014-05-07 9:26 ` Peter Maydell
2014-05-07 9:37 ` Alexander Graf
2014-05-07 9:40 ` Peter Maydell
2014-05-07 9:44 ` Alexander Graf
2014-05-07 9:41 ` Alexander Graf
2014-05-07 10:19 ` Greg Kurz
2014-05-07 11:54 ` Alexander Graf
2014-05-07 12:40 ` Greg Kurz
2014-05-07 13:04 ` Alexander Graf
2014-05-08 1:36 ` Rusty Russell
2014-05-05 8:07 ` [Qemu-devel] [PATCH v2 4/4] ppc64 dump: Set the correct endianness in ELF dump header Greg Kurz
2014-05-05 11:08 ` [Qemu-devel] [PATCH v3 0/4] little-endian dump for ppc64 Alexander Graf
2014-05-07 21:14 ` Andreas Färber
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=5369F864.7040406@suse.de \
--to=agraf@suse.de \
--cc=afaerber@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).