linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pawel Moll <pawel.moll@arm.com>
To: Marc Zyngier <Marc.Zyngier@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"virtualization@lists.linux-foundation.org" 
	<virtualization@lists.linux-foundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [RFC PATCH] virt_mmio: fix signature checking for BE guests
Date: Wed, 13 Feb 2013 15:08:22 +0000	[thread overview]
Message-ID: <1360768102.4045.107.camel@hornet> (raw)
In-Reply-To: <1360765538-18097-1-git-send-email-marc.zyngier@arm.com>

On Wed, 2013-02-13 at 14:25 +0000, Marc Zyngier wrote:
> Using readl() to read the magic value and then memcmp() to check it
> fails on BE, as bytes will be the other way around (by virtue of
> the registers to follow the endianess of the guest).

Hm. Interesting. I missed the fact that readl() as a "PCI operation"
will always assume LE values...

> Fix it by encoding the magic as an integer instead of a string.
> So I'm not completely sure this is the right fix, 

It seems right, however...

> - Using __raw_readl() instead. Is that a generic enough API?
> 
... this implies that either the spec is wrong (as it should say: the
device registers are always LE, in the PCI spirit) or all readl()s & co.
should be replaced with __raw equivalents.

Having said that, does the change make everything else work with a BE
guest? (I assume we're talking about the guest being BE, right? ;-) If
so it means that the host is not following the current spec and it
treats all the registers as LE.

> - Reading the MAGIC register byte by byte. Is that allowed? The spec
>   only says it is 32bit wide.

And the spirit of the spec was: _exactly 32bit wide_. It's just simpler
to implement one access width on the host side.

Paweł



  reply	other threads:[~2013-02-13 15:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 14:25 [RFC PATCH] virt_mmio: fix signature checking for BE guests Marc Zyngier
2013-02-13 15:08 ` Pawel Moll [this message]
2013-02-13 15:28   ` Marc Zyngier
2013-02-13 15:46     ` Pawel Moll
2013-02-13 16:40       ` Marc Zyngier
2013-02-13 16:53     ` Michael S. Tsirkin
2013-02-13 17:04       ` Marc Zyngier
2013-02-14  0:22       ` Rusty Russell
2013-02-14 10:54         ` [PATCH] virtio-spec: Define virtio-mmio registers as LE Pawel Moll
2013-02-15  3:57           ` Rusty Russell
2013-03-01 10:41           ` Marc Zyngier
2013-03-01 10:50             ` Pawel Moll
2013-03-01 11:21               ` Marc Zyngier
2013-03-01 12:37                 ` Pawel Moll
2013-03-01 13:16                   ` Marc Zyngier
2013-03-05  0:11                   ` Rusty Russell
2013-03-06 15:10                     ` Pawel Moll
2013-03-07  6:36                       ` Rusty Russell
2013-02-15  0:07     ` [RFC PATCH] virt_mmio: fix signature checking for BE guests Benjamin Herrenschmidt

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=1360768102.4045.107.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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).