From: Kenneth Johansson <kenneth@southpole.se>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: kexec on e300 core / mpc5121
Date: Thu, 06 Aug 2009 00:49:45 +0200 [thread overview]
Message-ID: <1249512585.13069.9.camel@localhost> (raw)
In-Reply-To: <20090804230605.GA28753@Chamillionaire.breakpoint.cc>
On Wed, 2009-08-05 at 01:06 +0200, Sebastian Andrzej Siewior wrote:
> I've tried kexec on e300 core which should be easy since it is possible
> to disable the MMU on that core. However it does not work.
Is it not possible to disable the mmu on all cpu's that have one ??
> Once I disable the MMU, I can't access my MBAR and print chars on the
> serial port. Is this "normal" or do I have still some caches on?
Yes cache and mmu is separate. the 5121 is not cache coherent and do not
limit cache to only memory regions so serial port or any memory mapped
register is a no no unless you have cache off or cache on and mmu on
with a correct setting for what address range to cache.
Before you turn off the cache you need to flush out all dirty data. best
done by simply reading in 32kb of crap from somewhere. otherwise you are
sure to loose at least the stack and you do not want that.
next prev parent reply other threads:[~2009-08-05 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 23:06 kexec on e300 core / mpc5121 Sebastian Andrzej Siewior
2009-08-05 21:33 ` Sebastian Andrzej Siewior
2009-08-05 22:49 ` Kenneth Johansson [this message]
2009-08-05 23:47 ` Scott Wood
2009-08-06 0:20 ` Kenneth Johansson
2009-08-06 7:25 ` Sebastian Andrzej Siewior
2009-08-06 15:54 ` Scott Wood
2009-08-06 13:58 ` Kumar Gala
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=1249512585.13069.9.camel@localhost \
--to=kenneth@southpole.se \
--cc=linuxppc-dev@ozlabs.org \
--cc=sebastian@breakpoint.cc \
/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).