From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: Simply disabling MMU in cpu_v7_reset doesn't work for kexec
Date: Wed, 21 Apr 2010 22:10:17 +0100 [thread overview]
Message-ID: <20100421211017.GA27575@shareable.org> (raw)
In-Reply-To: <20100421194844.GF26616@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Wed, Apr 21, 2010 at 09:19:06PM +0800, Eric Miao wrote:
> > On Wed, Apr 21, 2010 at 9:18 PM, Eric Miao <eric.y.miao@gmail.com> wrote:
> > > Tried the following simple code to disable MMU in cpu_v7_reset() doesn't
> > > seem to work for kexec reboot. I was expecting the following instructions
> > > after MMU is disabled are still reachable in the instruction fetching pipe.
> > >
> >
> > .align 5
> > ENTRY(cpu_v7_reset)
> > + mrc p15, 0, r1, c1, c0, 0 @ ctrl register
> > + bic r1, r1, #0x0001 @ ...............m
> > + mcr p15, 0, r1, c1, c0, 0 @ disable MMU
> > + mcr p15, 0, ip, c8, c7, 0 @ invalidate I and D TLBs
> > mov pc, r0
> > ENDPROC(cpu_v7_reset)
>
> The procedure expected here is:
>
> 1. invalidate caches
> 2. drain buffers
> 3. invalidate TLBs
> 4. disable MMU et.al.
> 5. jump to the address in r0.
>
> The reason this is permitted is because cpu_v7_proc_fin _must_ be called
> before hand, which is expected to disable all interrupts, and flush and
> disable the caches.
Isn't step 1 above redundant, because caches are already disabled and
flushed?
> It might be worth given the speculative behaviour of V7 to also invalidate
> TLBs after a dsb and isb after step 4 instead of before step 4 - and (iirc)
> also doing an isb after invalidating the TLBs.
Mightn't the CPU refill one entry in the TLB between steps 3 and 4,
just by fetching the instructions - even non-speculatively?
Fwiw, the lengthy patch here:
http://lists.infradead.org/pipermail/barebox/2010-January/000528.html
does exactly this in the ARMv7 part:
1. Turn off MMU and caches (one mcr).
2. Clean and flush caches.
3. Invalidate TLBs.
4. Invalidate BTC.
5. DSB.
6. ISB.
7. Return to caller / destination.
I don't know if it expects the final instructions to be direct-mapped.
-- Jamie
next prev parent reply other threads:[~2010-04-21 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 13:18 Simply disabling MMU in cpu_v7_reset doesn't work for kexec Eric Miao
2010-04-21 13:19 ` Eric Miao
2010-04-21 19:25 ` Jamie Lokier
2010-04-21 19:48 ` Russell King - ARM Linux
2010-04-21 21:10 ` Jamie Lokier [this message]
2010-04-21 21:39 ` 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=20100421211017.GA27575@shareable.org \
--to=jamie@shareable.org \
--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.