From: "Xianghua Xiao" <x.xiao@freescale.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Cache-inhibited region for certain exception handler(e500 chips, 2.4 kernel)?
Date: Wed, 15 Feb 2006 16:06:41 -0600 [thread overview]
Message-ID: <000201c6327c$1a2b80f0$b07c520a@fsl.freescale.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Is there a way to put certain exception handler(e.g. machine check) on e500
to a cache-inhibited region?
1. The e500 kernel puts exception handlers at the starting of the physical
memory.
2. All the physical memory are covered by a few TLB1s to do
0xc0000000-0x00000000 translation.
3. We can not add a new TLB1 to map a small piece of memory, because it has
boundary limitation(4K...256M). We can not use two TLB1 to overlap since it
will cause program error.
4. When we tried to move a handler(e.g. machine check) to a different
location, the kernel won't boot.
5. We don't want to map all the exceptional handlers to be cache inhibited,
say, the first 1MB, the performance will be horrible if we do so.
Is there a way at all to tweak things like this, i.e., put an exception
handler into a piece of memory that is cache-inhibited?
I also thought about use mlock/mmap on /dev/mem, move the specific exception
handler to a high address then use a separate TLB1 to cover it(need change
link script?),etc.
Any suggestion is greatly appreciated.
xianghua
[-- Attachment #2: Type: text/html, Size: 2687 bytes --]
next reply other threads:[~2006-02-15 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 22:06 Xianghua Xiao [this message]
2006-02-15 23:25 ` Cache-inhibited region for certain exception handler(e500 chips, 2.4 kernel)? Kumar Gala
2006-02-15 23:50 ` PowerQUICC II Pro MPC8349E-MDS Linux 2.6 support David Hawkins
2006-02-15 23:45 ` Kumar Gala
2006-02-16 0:01 ` David Hawkins
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='000201c6327c$1a2b80f0$b07c520a@fsl.freescale.net' \
--to=x.xiao@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=risc10@freescale.com \
/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).