RE: what will be caused by setting TLB's virtual address part to unmapped address?

["Uhler, Mike" <uhler@mips.com>]

What you're seeing is the standard sequence used to initialize the TLB.  The processor doesn't look at entries for kseg0, so those TLB entries are ignored.

/gmu
---
Michael Uhler, Chief Technology Officer
MIPS Technologies, Inc.   Email: uhler at mips dot com
1225 Charleston Road      Voice:  (650)567-5025
Mountain View, CA 94043

-----Original Message-----
From: linux-mips-bounce@linux-mips.org [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Bin Chen
Sent: Monday, April 24, 2006 8:14 AM
To: linux-mips@linux-mips.org
Subject: what will be caused by setting TLB's virtual address part to unmapped address?

> Hi,
>
> In 
>   MIPS64, the 0xFFFFFFFF80000000 is a kernel unmapped area, what will be caused 
>   by setting up a TLB entry with the virtual address be 
>   0xFFFFFFFF80000000?
>
> I ask this question because I noticed u-boot's TLB 
>   init code use the address from 0xFFFFFFFF80000000 to fill in the blank tlb, 
>   but I don't know the purpose of this operation.
>
> Thanks in 
>   advance.
>
> B.C