From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Victor Kamensky <victor.kamensky@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Falcon <tlfalcon@linux.vnet.ibm.com>,
kvm-devel <kvm@vger.kernel.org>,
QEMU Developers <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] KVM and variable-endianness guest CPUs
Date: Tue, 28 Jan 2014 11:32:41 +1100 [thread overview]
Message-ID: <1390869161.3872.42.camel@pasglop> (raw)
In-Reply-To: <CAA3XUr2yv2aoOjXoWSUU4Ze7N+RUXOYm6DgWKh9iSOREaSfRTA@mail.gmail.com>
On Thu, 2014-01-23 at 20:11 -0800, Victor Kamensky wrote:
> > I would take 50 byteswaps with a clear ABI any day over an obscure
> > standard that can avoid a single hardware-on-register instruction.
> This
> > is about designing a clean software interface, not about building an
> > optimized integrated stack.
> >
> > Unfortunately, this is going nowhere, so I think we need to stop
> this
> > thread. As you can see I have sent a patch as a clarification to
> the
> > ABI, if it's merged we can move on with more important tasks.
>
> OK, that is fine. I still believe is not the best choice,
> but I agree that we need to move on. I will respin my
> V7 KVM BE patches according to this new semantics, I will
> integrate comments that you (thanks!) and others gave me
> over mailing list and post my series again when it is ready.
Right, the whole "host endian" is a horrible choice from every way you
look at it, but I'm afraid it's unfixable since it's already ABI :-(
Ben.
next prev parent reply other threads:[~2014-01-28 0:33 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 17:53 [Qemu-devel] KVM and variable-endianness guest CPUs Peter Maydell
2014-01-17 18:52 ` Peter Maydell
2014-01-18 4:24 ` Christoffer Dall
2014-01-18 7:32 ` Alexander Graf
2014-01-18 10:15 ` Peter Maydell
2014-01-20 14:20 ` Alexander Graf
2014-01-20 14:31 ` Peter Maydell
2014-01-20 14:22 ` Alexander Graf
2014-01-20 19:19 ` Christoffer Dall
2014-01-22 5:39 ` Victor Kamensky
2014-01-22 6:31 ` Anup Patel
2014-01-22 6:41 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-01-22 7:26 ` Victor Kamensky
2014-01-22 10:52 ` Alexander Graf
2014-01-23 4:25 ` Victor Kamensky
2014-01-23 10:32 ` Alexander Graf
2014-01-23 10:56 ` Greg Kurz
2014-01-22 8:57 ` Anup Patel
2014-01-23 23:28 ` Christoffer Dall
2014-01-22 10:22 ` [Qemu-devel] " Peter Maydell
2014-01-22 17:19 ` Victor Kamensky
2014-01-22 17:29 ` Peter Maydell
2014-01-22 19:29 ` Victor Kamensky
2014-01-22 20:02 ` Peter Maydell
2014-01-22 22:47 ` Victor Kamensky
2014-01-22 23:18 ` Peter Maydell
2014-01-23 0:22 ` Victor Kamensky
2014-01-23 10:23 ` Peter Maydell
2014-01-23 15:06 ` Victor Kamensky
2014-01-23 15:33 ` Peter Maydell
2014-01-23 16:25 ` Victor Kamensky
2014-01-23 20:45 ` Christoffer Dall
2014-01-24 0:50 ` Victor Kamensky
2014-01-24 2:14 ` Christoffer Dall
2014-01-24 4:11 ` Victor Kamensky
2014-01-28 0:32 ` Benjamin Herrenschmidt [this message]
2014-01-28 0:40 ` [Qemu-devel] [Qemu-ppc] " Christoffer Dall
2014-01-28 0:15 ` Benjamin Herrenschmidt
2014-01-24 0:09 ` [Qemu-devel] " Victor Kamensky
2014-01-28 0:07 ` [Qemu-devel] [Qemu-ppc] " Benjamin Herrenschmidt
2014-01-28 0:07 ` Benjamin Herrenschmidt
2014-01-27 23:34 ` Benjamin Herrenschmidt
2014-01-27 23:49 ` Peter Maydell
2014-01-28 0:36 ` Benjamin Herrenschmidt
2014-01-28 0:44 ` Christoffer Dall
2014-01-28 4:47 ` Benjamin Herrenschmidt
2014-01-28 16:31 ` Christoffer Dall
2014-01-27 23:31 ` Benjamin Herrenschmidt
2014-01-27 23:27 ` Benjamin Herrenschmidt
2014-01-28 9:16 ` Avi Kivity
2014-01-28 9:04 ` [Qemu-devel] " Avi Kivity
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=1390869161.3872.42.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=victor.kamensky@linaro.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).