From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Implement cpu_v7_reset.
Date: Thu, 2 Sep 2010 09:43:53 +0100 [thread overview]
Message-ID: <20100902084353.GB26319@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100902050349.GA14214@pengutronix.de>
On Thu, Sep 02, 2010 at 07:03:49AM +0200, Uwe Kleine-K?nig wrote:
> Hello,
>
> > > +#ifdef CONFIG_MMU
> > > + mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs
> > > +#endif
> > > + mrc p15, 0, ip, c1, c0, 0 @ ctrl register
> > > + bic ip, ip, #0x000f @ ............wcam
> > > + bic ip, ip, #0x1100 @ ...i...s........
> > > + mcr p15, 0, ip, c1, c0, 0 @ ctrl register
> >
> > On a related note, I was always a bit confused since proc-v6 and proc-v7
> > don't turn off the MMU in their cpu_reset functions, which doesn't seem
> > correct with respect to Documentation/arm/Booting. Is it necessary to
> > turn off the MMU when kexec'ing the kernel? Last time I tried kexec'ing
> > on a v6 it worked fine without turning off the MMU.
> The boot process isn't that strict.
Wrong. The boot process _is_ that strict. If the MMU is left on, you
need to have page tables present, and ensure that these aren't overwritten.
We make no guarantees on that, and there's no way to tell the following
kernel not to touch that area.
The only thing that's guaranteed is to turn the MMU off, as per the boot
process.
What just happens to work does not mean that "it's not that strict".
next prev parent reply other threads:[~2010-09-02 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 14:01 [PATCH] ARM: Implement cpu_v7_reset Linus Walleij
2010-09-01 21:18 ` Stephen Boyd
2010-09-02 5:03 ` Uwe Kleine-König
2010-09-02 8:43 ` Russell King - ARM Linux [this message]
2010-09-01 23:23 ` Russell King - ARM Linux
2010-09-02 8:34 ` Mika Westerberg
2010-09-02 8:41 ` Russell King - ARM Linux
2010-09-02 8:53 ` Mika Westerberg
2010-09-02 10:39 ` Russell King - ARM Linux
2010-09-02 11:52 ` Mika Westerberg
2010-09-02 12:18 ` Russell King - ARM Linux
2010-09-02 13:48 ` Mika Westerberg
2010-09-03 6:04 ` Mika Westerberg
2010-09-06 8:58 ` Per Fransson
2010-09-06 17:24 ` Mika Westerberg
2010-09-02 13:30 ` Per Fransson
2010-09-03 18:17 ` Per Fransson
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=20100902084353.GB26319@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).