All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] Fix g2h() for 32-bit targets on 64-bit hosts
Date: Wed, 03 Aug 2016 20:18:32 +1000	[thread overview]
Message-ID: <1470219512.12584.78.camel@kernel.crashing.org> (raw)
In-Reply-To: <1470217830.12584.70.camel@kernel.crashing.org>

On Wed, 2016-08-03 at 19:50 +1000, Benjamin Herrenschmidt wrote:
> 
> > I'm confused. Is this just swapping the order of the operands to
> > '+'?
> > I wouldn't expect that to make any difference because typecast has
> > higher precedence than '+'...
> 
> The typecast to target_ulong which is 32-bits :-)

But you are right, this isn't the breakage. Patch 1/2 is sufficient
to fix it, though I didn't realize it at first.

"vaddr" is actually a typedef, so the whole tlb_vaddr_to_host() turned
into a cast of guest_base to vaddr...

The g2h part was just me being tired. It's true though that
target_ulong is going to be 32-bits which I don't like but
type promotion makes it work.

So drop that patch and stick to patch 1/2 which is the real fix.

As to why you don't hit the bug on ARM, well, maybe you don't 
many helpers using tlb_vaddr_to_host ? Also address randomization makes
things hit or miss here ...

Cheers,
Ben.

  reply	other threads:[~2016-08-03 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  3:15 [Qemu-devel] [PATCH 2/2] Fix g2h() for 32-bit targets on 64-bit hosts Benjamin Herrenschmidt
2016-08-03  8:40 ` Peter Maydell
2016-08-03  9:50   ` Benjamin Herrenschmidt
2016-08-03 10:18     ` Benjamin Herrenschmidt [this message]
2016-08-03 10:48       ` Peter Maydell
2016-08-03 10:51         ` 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=1470219512.12584.78.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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 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.