All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Mike Uhler <uhler@mips.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Dominic Sweetman <dom@mips.com>,
	linux-mips@linux-mips.org
Subject: Re: [patch] Use XKPHYS for 64-bit TLB flushes
Date: Wed, 8 Jan 2003 20:44:08 +0100	[thread overview]
Message-ID: <20030108204408.A27888@linux-mips.org> (raw)
In-Reply-To: <200301081933.h08JX1F09754@uhler-linux.mips.com>; from uhler@mips.com on Wed, Jan 08, 2003 at 11:33:01AM -0800

On Wed, Jan 08, 2003 at 11:33:01AM -0800, Mike Uhler wrote:

> >  They do are different: KSEG0+entry*0x2000, likewise for XKPHYS -- see the
> > patch. 
> 
> This is precisely what we use for our internal testing (which is also
> exported to MIPS32 and MIPS64 architecture licensees) to initialize the
> TLB.  I have not yet seen a case where this fails, and would be interested
> in hearing about any case where it does fail.

We used to use just KSEG0 instead of KSEG0+entry*0x2000.  That was running
fine over years but had to be changed for the sake of two CPUs afair.  There
was some discussion on this list about this and I accepted the change by that
time because Kevin imho correctly argued that the spec left it unspecified
if an implementation is feeding addresses in an unmapped address space
though the TLB.

  Ralf

  reply	other threads:[~2003-01-08 19:44 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 [this message]
2003-01-08 20:12           ` Maciej W. Rozycki
2003-01-09  1:36             ` Ralf Baechle
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=20030108204408.A27888@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 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.