All of lore.kernel.org
 help / color / mirror / Atom feed
From: brad@heeltoe.com (Brad Parker)
To: linux-arm-kernel@lists.infradead.org
Subject: armv7 + lpae broken in 4.1.12+ ?
Date: Fri, 27 Nov 2015 10:55:35 -0500	[thread overview]
Message-ID: <56587CF7.9060302@heeltoe.com> (raw)
In-Reply-To: <20151127093601.GA25781@arm.com>

On 11/27/15 4:36 AM, Will Deacon wrote:> As Russell says, AEABI requires 
the 64-bit pte value to be passed in > r2 and r3 for cpu_v7_set_pte_ext: 
 > > C.3 If the argument requires double-word alignment (8-byte), the > 
NCRN is rounded up to the next even register number. > >> The simple fix 
is to add "mov r3, r2; mov r2,r1" at the begining >> of 
cpu_v7_set_pte_ext(), but that's a hack (but it does solve the >> 
problem and the kernel boots). > > ... so this would actually cause 
breakage for other people. > > Which toolchain are you using?
[sorry for the re-send;  I keep getting bounced by the email.html 
filter; not sure why]

That all makes sense. I'm using a linaro toolchain (which I'll admit I
grabbed because I was lazy)

gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/arm-linux-gnueabihf-

It seems really odd.  I would have thought "gnueabihf" would be EABI, so
a 64 bit arg should be in r2,r3; but it's not.  It's in r1, r2.

could something in my .config cause this?  (I'd be surprised if that were the case, but...).

I'm happy to try a better toolchain if you can point me to one (binary).

-brad

  reply	other threads:[~2015-11-27 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 23:26 armv7 + lpae broken in 4.1.12+ ? Brad Parker
2015-11-26 23:37 ` Russell King - ARM Linux
2015-11-27  9:36 ` Will Deacon
2015-11-27 15:55   ` Brad Parker [this message]
2015-11-27 16:06     ` Russell King - ARM Linux
2015-11-27 17:02       ` Brad Parker
2015-11-27 17:09         ` Russell King - ARM Linux

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=56587CF7.9060302@heeltoe.com \
    --to=brad@heeltoe.com \
    --cc=linux-arm-kernel@lists.infradead.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.