From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Enable the mmu in start_secondary()
Date: Mon, 29 Mar 2010 03:16:33 +0000 [thread overview]
Message-ID: <20100329031633.GC26500@linux-sh.org> (raw)
In-Reply-To: <a460f3c9762b32919a8886a12ecaf3347358234d.1269806815.git.matt@console-pimps.org>
On Sun, Mar 28, 2010 at 09:08:25PM +0100, Matt Fleming wrote:
> For the boot, enable_mmu() is called from setup_arch() but we don't call
> setup_arch() for any of the other cpus. So turn on the non-boot cpu's
> mmu inside of start_secondary().
>
> I noticed this bug on an SMP board when trying to map I/O memory
> (smsc911x registers) into the kernel address space. Since the Address
> Translation bit in MMUCR wasn't set, accessing the virtual address where
> the smsc911x registers were supposedly mapped actually performed a
> physical address access.
>
> Signed-off-by: Matt Fleming <matt@console-pimps.org>
Applied, thanks.
prev parent reply other threads:[~2010-03-29 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 20:08 [PATCH] sh: Enable the mmu in start_secondary() Matt Fleming
2010-03-29 3:16 ` Paul Mundt [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=20100329031633.GC26500@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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).