From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"qemu-ppc@nongnu.org list:PowerPC" <qemu-ppc@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] target-ppc: ppc64 target's virtio can be either endian.
Date: Tue, 10 Dec 2013 06:44:04 +1100 [thread overview]
Message-ID: <1386618244.5159.74.camel@pasglop> (raw)
In-Reply-To: <52603062-FAEC-4D6C-8F56-112488CCBAA9@suse.de>
On Mon, 2013-12-09 at 16:33 +0100, Alexander Graf wrote:
>
> Also can't virtio_get_byteswap pass in the CPU pointer of the CPU
> that's calling in this moment? I'm not sure how racy it is to
> synchronize the first cpu while we're not in the first cpu's execution
> thread.
The LPCR bit is always set on all CPUs.
> Either way, if we do this "right" we don't even have to jump through
> these hoops, as little endian setting simply happens steered from
> QEMU, so QEMU will have all knowledge about the guest's little endian
> mode without the need to synchronize any state.
Ben.
next prev parent reply other threads:[~2013-12-09 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 15:35 [Qemu-devel] [PATCH] target-ppc: ppc64 target's virtio can be either endian Greg Kurz
2013-12-09 15:33 ` Alexander Graf
2013-12-09 17:11 ` Greg Kurz
2013-12-09 17:18 ` Alexander Graf
2013-12-10 17:37 ` Greg Kurz
2013-12-10 17:48 ` Alexander Graf
2013-12-10 19:44 ` Greg Kurz
2013-12-10 22:25 ` Alexander Graf
2013-12-11 15:59 ` [Qemu-devel] [PATCH V2] " Greg Kurz
2013-12-11 16:11 ` Alexander Graf
2013-12-11 17:18 ` Greg Kurz
2014-01-17 13:52 ` [Qemu-devel] [PATCH] target-ppc: ppc64 target's virtio can be either endian. (v3) Greg Kurz
2014-01-20 14:36 ` Alexander Graf
2013-12-09 19:44 ` Benjamin Herrenschmidt [this message]
2013-12-10 1:18 ` [Qemu-devel] [Qemu-ppc] [PATCH] target-ppc: ppc64 target's virtio can be either endian Alexander Graf
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=1386618244.5159.74.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.