From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: "Rusty Russell" <rusty@rustcorp.com.au>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"bharata@linux.vnet.ibm.com" <bharata@linux.vnet.ibm.com>,
"Andreas Färber" <afaerber@suse.de>,
"Greg Kurz" <gkurz@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/4] target-ppc: ppc can be either endian
Date: Wed, 7 May 2014 10:40:02 +0100 [thread overview]
Message-ID: <CAFEAcA9bYS_vPHFgCy=rP3ajDb0o7bgx3Ww91xVHEobSKMR=0g@mail.gmail.com> (raw)
In-Reply-To: <01A509C3-B5E8-421E-8C12-E30A36AB1503@suse.de>
On 7 May 2014 10:37, Alexander Graf <agraf@suse.de> wrote:
>
>
>> Am 07.05.2014 um 11:26 schrieb Peter Maydell <peter.maydell@linaro.org>:
>>
>>> On 7 May 2014 10:09, Alexander Graf <agraf@suse.de> wrote:
>>> I don't think we should overengineer hacks for legacy virtio.
>>
>> Agreed. So what's our final conclusion: virtio endianness
>> is the endianness of the guest kernel at the point where
>> it triggers a reset of the virtio device, yes?
>
> The interrupt endianness for book3s PPC. Since that's an arch
> specific thing I think we should just make the determination
> mechanism arch dependent and list it in the spec.
>
> Booke for example would be vastly different since there is no
> global LE flag - it's a bit in the TLB entries.
Sure, but I think we should also state the general principle
we're aiming to implement with the arch specific detail,
so that people figuring out what a new arch should do
have a guide to follow.
thanks
-- PMM
next prev parent reply other threads:[~2014-05-07 9:40 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
2014-05-07 9:26 ` Peter Maydell
2014-05-07 9:37 ` Alexander Graf
2014-05-07 9:40 ` Peter Maydell [this message]
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='CAFEAcA9bYS_vPHFgCy=rP3ajDb0o7bgx3Ww91xVHEobSKMR=0g@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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).