From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] Use XKPHYS for 64-bit TLB flushes
Date: Wed, 8 Jan 2003 14:59:53 +0100 [thread overview]
Message-ID: <20030108145953.B8396@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030108141332.1580F-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, Jan 08, 2003 at 02:27:05PM +0100
On Wed, Jan 08, 2003 at 02:27:05PM +0100, Maciej W. Rozycki wrote:
> 32-bit R4k TLB flush functions use KSEG0 as an impossible (unmapped) VPN2
> value for invalidated TLB entries. 64-bit ones use KSEG0 as well, but
> here KSEG0 is a valid XKSEG (mapped) value as it gets interpreted as
> 0xc00000ff80000000 when written into cp0.EntryHi. The correct impossible
> (unmapped) VPN2 value for the 64-bit mode is XKPHYS.
That's a funny one. Historically the idea was to use KSEG0 because the
for KSEG0 the TLB is not used for translation. That already failed for
the Sibyte SB1 which is why we have to use different KSEG0 addresses for
each entry there.
> Here is a patch implementing it. The code runs fine on my R4400SC. OK
> to apply?
Yes.
> BTW, show_tlb() (in the same file) is buggy and redundant --
> dump_tlb_all() is a correct equivalent. I'd like to remove show_tlb() --
> OK?
Yes. I'd eventually like to move the tlb dump functions away from the
lib directory into the mm directory which seems to be more the right
place for them.
Ralf
next prev parent reply other threads:[~2003-01-08 14:00 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 [this message]
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
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=20030108145953.B8396@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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.