All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@uga.edu>
To: sparclinux@vger.kernel.org
Subject: Re: TLB miss handler code
Date: Mon, 19 Jan 2004 21:27:13 +0000	[thread overview]
Message-ID: <87brozd3ym.fsf@uga.edu> (raw)
In-Reply-To: <Pine.GSO.4.43.0401191315430.13707-100000@gatekeeper.ececs.uc.edu>

Nawab Ali <alin@ececs.uc.edu> writes:

> Hi,
> I have a Sun Ultra-10 running Debian woody. I need to modify the TLB miss
> handler code. Basically everytime there is a TLB miss, I'm trying to log
> the new PTE that is brought into the TLB.
>
> I know that SPARC machines handle TLB refills in software. Can someone
> please point me to the TLB miss handler code(which file???) in the linux
> kernel(2.4.24)??? I'm a bit lost here.
>
> Any help would be greatly appreciated.

Well, I am not sure about 2.4.24, but in 2.6.0, the do_sparc64_fault
routine in arch/sparc64/mm/fault.c is invoked during TLB miss
handling.  When it's a TLB miss you can tell by the fact that
(fault_code & FAULT_CODE_DTLB || fault_code & FAULT_CODE_ITLB).

-- 
--Ed L Cashin            |   PGP public key:
  ecashin@uga.edu        |   http://noserose.net/e/pgp/


  reply	other threads:[~2004-01-19 21:27 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 [this message]
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
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=87brozd3ym.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.