Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Mike Uhler <uhler@mips.com>, Dominic Sweetman <dom@mips.com>,
	linux-mips@linux-mips.org
Subject: Re: [patch] Use XKPHYS for 64-bit TLB flushes
Date: Thu, 9 Jan 2003 02:36:01 +0100	[thread overview]
Message-ID: <20030109023601.A1213@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030108210002.11293A-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, Jan 08, 2003 at 09:12:03PM +0100

On Wed, Jan 08, 2003 at 09:12:03PM +0100, Maciej W. Rozycki wrote:

>  Well, like it or not, CAMs do not like multiple matches -- up to a
> physical damage even.  So they should be avoided if possible.  While KSEG0
> won't match for any real address translation, there is a non-zero
> probability of executing a tlbp for it as a result of buggy code or
> execution gone wild (root running crashme?). 

I'm told the TLB Shutdown bit in the R4000 is basically implemented as an
overcurrent protection.  That is on many chips even a hit on several
entries won't cause a tlb shutdown until the matches do result in the
TLB drawing more than a certain current.

A tlbp on a KSEG0 address shouldn't happen.  If it's attempted we already
have worse problems.

  Ralf

  reply	other threads:[~2003-01-09  1:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 13:27 [patch] Use XKPHYS for 64-bit TLB flushes Maciej W. Rozycki
2003-01-08 13:59 ` Ralf Baechle
2003-01-08 19:02   ` Dominic Sweetman
2003-01-08 19:18     ` Maciej W. Rozycki
2003-01-08 19:33       ` Mike Uhler
2003-01-08 19:33         ` Mike Uhler
2003-01-08 19:44         ` Ralf Baechle
2003-01-08 20:12           ` Maciej W. Rozycki
2003-01-09  1:36             ` Ralf Baechle [this message]
2003-01-09 20:10           ` Carsten Langgaard

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=20030109023601.A1213@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dom@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=uhler@mips.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