From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: using identity_mapping_add & switching MMU state - how ?
Date: Sat, 4 Jun 2011 00:53:02 +0100 [thread overview]
Message-ID: <20110603235302.GA26822@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1106030834240.2311@localhost6.localdomain6>
On Fri, Jun 03, 2011 at 11:44:02AM +0100, Frank Hofmann wrote:
> On Thu, 2 Jun 2011, Russell King - ARM Linux wrote:
>> But... it requires the v:p offset in r1, and the _virtual_ address of
>> the code to continue at in lr. These are specifically saved for it by
>> cpu_suspend in arch/arm/kernel/sleep.S.
>
> I've read that - that's why the hibernation resume path has been written
> this way. I'm trying to create the conditions necessary, i.e. set up
> r0/r1/lr _and_ the MMU state in such a way that it's callable unmodified.
I think you missed my point. Go back and look at this bit of your code,
and indentify what _exactly_ is in r1 at the point cpu_do_resume is
called. I'll give you a hint - it's not the v:p offset as required.
ldr r2, =cpu_do_resume
sub r2, r1 @ __pa()
ldr r3, =.Lmmu_is_off
sub r3, r1 @ __pa()
sub r0, r1 @ __pa()
ldr lr, =.Lpost_mmu
mrc p15, 0, r1, c1, c0, 0
bic r1, #CR_M
mcr p15, 0, r1, c1, c0, 0 @ MMU OFF
mrc p15, 0, r1, c2, c0, 0 @ queue a dependency on CP15
sub pc, r3, r1, lsr #32 @ to local label, phys addr
.ltorg
.align 5
.Lmmu_is_off:
mov pc, r2 @ jump to phys cpu_v6_do_resume
next prev parent reply other threads:[~2011-06-03 23:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 15:44 using identity_mapping_add & switching MMU state - how ? Frank Hofmann
2011-06-02 16:20 ` Will Deacon
2011-06-02 16:22 ` Dave Martin
2011-06-02 16:46 ` Frank Hofmann
2011-06-02 18:07 ` Lorenzo Pieralisi
2011-06-03 12:20 ` Frank Hofmann
2011-06-02 20:16 ` Russell King - ARM Linux
2011-06-03 10:44 ` Frank Hofmann
2011-06-03 15:56 ` Frank Hofmann
2011-06-03 23:53 ` Russell King - ARM Linux [this message]
2011-06-06 16:32 ` Frank Hofmann
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=20110603235302.GA26822@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).