From: "David S. Miller" <davem@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: TLB miss handler code
Date: Thu, 22 Jan 2004 02:16:07 +0000 [thread overview]
Message-ID: <20040121181607.25f623b4.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.43.0401191315430.13707-100000@gatekeeper.ececs.uc.edu>
On Wed, 21 Jan 2004 21:15:58 -0500
Ed L Cashin <ecashin@uga.edu> wrote:
> Is it just that simple? Nawab Ali could, e.g., copy a section "S" of
> the trap handler code to a different part of the kernel and replace S
> with a jump to the new location. It would be a lot slower, I
> suppose.
>
> Then, with S in the regular kernel, he could add whatever he wanted,
> including jumps to C functions that he writes himself. That way he
> could write his own stuff in C with minimal modifications to the asm.
There are also very strict restrictions regarding register usage, you only
have 4 or 5 global registers to use, the other 2 or 3 global registers
have hardcoded values and furthermore if the VPTE_BASE mapping takes a TLB
miss the miss handler for that knows what values are precomputed in global
registers by the top-level TLB miss handler.
He cannot even touch any data structures as that would cause potential
recursive TLB misses and corrupt the current handler.
In short, I would only recommend this work to a true expert in Sparc v9
and UltraSPARC TLB programming. I myself would take a few long days to
implement said tracing support.
next prev parent reply other threads:[~2004-01-22 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 18:23 TLB miss handler code Nawab Ali
2004-01-19 21:27 ` Ed L Cashin
2004-01-20 23:46 ` Ben Collins
2004-01-21 0:33 ` Nawab Ali
2004-01-21 16:41 ` David S. Miller
2004-01-21 16:43 ` Ed L Cashin
2004-01-21 17:21 ` Ed L Cashin
2004-01-21 21:34 ` David S. Miller
2004-01-21 22:11 ` Ed L Cashin
2004-01-21 23:14 ` Nawab Ali
2004-01-22 1:52 ` David S. Miller
2004-01-22 2:15 ` Ed L Cashin
2004-01-22 2:16 ` David S. Miller [this message]
2004-01-22 5:01 ` Ed L Cashin
2004-01-22 5:24 ` Ed L Cashin
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=20040121181607.25f623b4.davem@redhat.com \
--to=davem@redhat.com \
--cc=sparclinux@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 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.