From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: disabling MMU of ARMv7-A
Date: Mon, 7 Apr 2014 18:16:24 +0100 [thread overview]
Message-ID: <20140407171624.GB3951@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20140407103312.GA7528@n2100.arm.linux.org.uk>
On Mon, Apr 07, 2014 at 11:33:12AM +0100, Russell King - ARM Linux wrote:
> On Mon, Apr 07, 2014 at 10:56:36AM +0100, Dave Martin wrote:
> > Agreed -- CONFIG_MMU=n does not need to imply that the MMU is turned off:
> > everything must be indentity-mapped (VA = PA), but it is still desirable
> > to define attributes. For SMP, it's *necessary* to define attributes,
> > otherwise we can't guarantee working spinlocks etc.
>
> It's also necessary for UP as well, as the load-exclusive and
> store-exclusive must still work. Remember these instructions get used
> for more than just spinlocks.
Agreed.
Nothing in head-nommu.S seems to create any initial page tables or
turn on the MMU, although we do set up an MPU instead if there is one,
Is !MMU known to work with v6 and later? I'm starting to have doubts.
My understanding of the ARM ARM is that a system may generate an abort
if ldrex/strex is attempted with the MMU off, though there are at least
some platforms that don't do that.
Cheers
---Dave
prev parent reply other threads:[~2014-04-07 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 7:15 disabling MMU of ARMv7-A Chanho Park
2014-03-28 7:23 ` Marc C
2014-03-28 7:27 ` Chanho Park
2014-03-28 10:49 ` Catalin Marinas
2014-03-28 10:43 ` Catalin Marinas
2014-04-07 9:56 ` Dave Martin
2014-04-07 10:33 ` Russell King - ARM Linux
2014-04-07 17:16 ` Dave Martin [this message]
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=20140407171624.GB3951@e103592.cambridge.arm.com \
--to=dave.martin@arm.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.