|Subject:||what will be caused by setting TLB's virtual address part to unmapped address?|
|From:||"Bin Chen" <firstname.lastname@example.org>|
|Date:||Mon, 24 Apr 2006 23:14:01 +0800|
|Domainkey-signature:||a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=NWSOh0DB/hLjkZrCo98mF9m/Imf68lDoDNbKt8o1ODWayVSDvHT+0+lXPg/kNHh1ZRRB4kStdfvmZMQJ+sRqVWG/pey6DTuPbFoMCfbZPvAuR4AMTVFvF8bOpekMGoIZN6H2VYlcCCeO3dAq6A5L8D6kr+Iw4avYuMsGgI1UrQw=|
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.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH] vr41xx: defconfig update, Yoichi Yuasa|
|Next by Date:||RE: what will be caused by setting TLB's virtual address part to unmapped address?, Uhler, Mike|
|Previous by Thread:||does the FTL/NTFL can be used with "GPL" licence?, zhuzhenhua|
|Next by Thread:||RE: what will be caused by setting TLB's virtual address part to unmapped address?, Uhler, Mike|
|Indexes:||[Date] [Thread] [Top] [All Lists]|