From: Ed L Cashin <ecashin@uga.edu>
To: sparclinux@vger.kernel.org
Subject: Re: TLB miss handler code
Date: Thu, 22 Jan 2004 02:15:58 +0000 [thread overview]
Message-ID: <87n08gaftt.fsf@uga.edu> (raw)
In-Reply-To: <Pine.GSO.4.43.0401191315430.13707-100000@gatekeeper.ececs.uc.edu>
"David S. Miller" <davem@redhat.com> writes:
> On Wed, 21 Jan 2004 18:14:05 -0500 (EST)
> Nawab Ali <alin@ececs.uc.edu> wrote:
>
>> Does it mean I'll have to muck around with the
>> arch/sparc64/kernel/{itlb,dtlb}_*.S files if I have to log(create a
>> tracefile) of all addresses that result in a TLB miss.
>
> That's exactly correct.
>
> In fact, you must not even change the number of instructions in these
> routines because they fit _PRECISELY_ into the sparc v9 trap table
> slots they are in. You would have to branch to some routine somewhere
> else in the kernel in order to add even one extra instruction of code.
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.
--
--Ed L Cashin | PGP public key:
ecashin@uga.edu | http://noserose.net/e/pgp/
next prev parent reply other threads:[~2004-01-22 2:15 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 [this message]
2004-01-22 2:16 ` David S. Miller
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=87n08gaftt.fsf@uga.edu \
--to=ecashin@uga.edu \
--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.