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


> 
>  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.

/gmu

-- 

  =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Michael Uhler, VP, Systems, Architecture, and Software Products 
  MIPS Technologies, Inc.   Email: uhler@mips.com   Pager: uhler_p@mips.com
  1225 Charleston Road      Voice:  (650)567-5025   FAX:   (650)567-5225
  Mountain View, CA 94043   Mobile: (650)868-6870   Admin: (650)567-5085

WARNING: multiple messages have this Message-ID (diff)
From: "Mike Uhler" <uhler@mips.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Dominic Sweetman <dom@mips.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, uhler@mips.com
Subject: Re: [patch] Use XKPHYS for 64-bit TLB flushes
Date: Wed, 08 Jan 2003 11:33:01 -0800	[thread overview]
Message-ID: <200301081933.h08JX1F09754@uhler-linux.mips.com> (raw)
Message-ID: <20030108193301.X22jIDJINIt1QTyBdX1zS-_b01gZ_mITLAJYaFwLvFA@z> (raw)
In-Reply-To: Your message of "Wed, 08 Jan 2003 20:18:46 +0100." <Pine.GSO.3.96.1030108200826.7872A-100000@delta.ds2.pg.gda.pl>


> 
>  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.

/gmu

-- 

  =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Michael Uhler, VP, Systems, Architecture, and Software Products 
  MIPS Technologies, Inc.   Email: uhler@mips.com   Pager: uhler_p@mips.com
  1225 Charleston Road      Voice:  (650)567-5025   FAX:   (650)567-5225
  Mountain View, CA 94043   Mobile: (650)868-6870   Admin: (650)567-5085

  reply	other threads:[~2003-01-08 19:34 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 [this message]
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
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=200301081933.h08JX1F09754@uhler-linux.mips.com \
    --to=uhler@mips.com \
    --cc=dom@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ralf@linux-mips.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.