From: brad@heeltoe.com (Brad Parker)
To: linux-arm-kernel@lists.infradead.org
Subject: armv7 + lpae broken in 4.1.12+ ?
Date: Thu, 26 Nov 2015 18:26:38 -0500 [thread overview]
Message-ID: <5657952E.906@heeltoe.com> (raw)
I was recently building a 4.1.12 kernel for a generic V7 platform with
LPAE. I could not get it to boot and then discovered two things:
- the early printk code in tty/serial call ioremap very early and it
fails because there's no heap
- the code in proc-v7-3level.S/cpu_v7_set_pte_ext doesn't work
The printk issue is no big deal. The pte issue is more important.
I found that the pte entries were garbage, which really confused me. I
finally discovered that the code in proc-v7-3level.S expects data in r0,
r2 & r3, but in fact it comes in on r0, r1 & r2.
My guess is that this is some vestige of the change made to
cpu_v7_switch_mm() some time ago to make the PA a 64 bit value (hence
using r0,r1). But this change was not made to cpu_v7_set_pte_ext, so it
writes garbage.
lol. I guess I'm the only one who turns on LPAE for v7 cpu's...
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).
I suspect the "right thing" is to make the prototype for
cpu_v7_set_pte_ext() in proc-fns.h use a phys_addr_t but I have not
tried that yet.
Can someone confirm that what I am seeing is correct?
-brad
next reply other threads:[~2015-11-26 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 23:26 Brad Parker [this message]
2015-11-26 23:37 ` armv7 + lpae broken in 4.1.12+ ? Russell King - ARM Linux
2015-11-27 9:36 ` Will Deacon
2015-11-27 15:55 ` Brad Parker
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=5657952E.906@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 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).