linux-mips
[Top] [All Lists]

Re: why it not write those 6bits to entrylo0/1 register?

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: why it not write those 6bits to entrylo0/1 register?
From: figo zhang <figo1802@gmail.com>
Date: Tue, 17 Nov 2009 17:37:25 +0800
Cc: linux-mips@linux-mips.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=EXHeoVl2/cKY+2IwnArpxxkHQXpb92ZIa/avgAkvE2E=; b=lcjM0yvOn8z4K+XrfA1Ijra0nfDBdpjUXrO9b3Y4MP0gbYArai9GTjQcTPOq1GxT+2 AaOJssI92LPQvEwFnVQiGqnr+jp6aBgBzu2+MKVra6MuDaqfssPPxIxaMwzsvmQEGQk3 QURby79YcZxpEQZ00PPOkT4TaCdfExIxnwq7c=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=e7gMqQhZuHyh5wXuld5tkPkwoqGoiJKy8o5tdrHP7t037ABs3RH8zPgISy5WMKWSFm rchFGwVa+KM1i9tY3tK2ocqQZDAKvu27CbslMaxig6PWEhcZ6SDAjTC46+MfkGJCY788 3ybVi92pAbUi3C25TlGmeVTo4yYb245nyESQ0=
In-reply-to: <20091117092601.GB2923@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <c6ed1ac50911170012u7a52fbb9h1ae62cabf766122f@mail.gmail.com> <20091117084047.GA2923@linux-mips.org> <c6ed1ac50911170059w600de299kfe4d79916547d809@mail.gmail.com> <20091117092601.GB2923@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org


2009/11/17 Ralf Baechle <ralf@linux-mips.org>
On Tue, Nov 17, 2009 at 04:59:59PM +0800, figo zhang wrote:

> > > why this right shift 6 bits? this 6 bits contain some important bit, such
> > > as:
> > > C: [bit3~5]: cohereny attribute of page
> >
> > No, the low 6 bits contain other information maintained by the kernel.
> > Shifting right by 6 bits is used to drop these software bits.  The
> > hardware bits are stored in bits 6 and up in a pte so the shift operation
> > is going to move them into the right place.
> >
>
> But i have see the kernel code: include/asm-mips/pgtable-bits.h:
> #define _CACHE_UNCACHED             (2<<3)
> #define _CACHE_CACHABLE_NONCOHERENT (3<<3)
> #define _CACHE_CACHABLE_COW         (3<<3)  /* Au1x                    */

This is code for the special case where CONFIG_64BIT_PHYS_ADDR and
CONFIG_CPU_MIPS32 are both defined.  In that case tlb-r4k.c also won't do
shifting.

> in include/asm-mips/pgtbale.h:
> #define PAGE_READONLY __pgprot(_PAGE_PRESENT | _PAGE_READ | \
>    PAGE_CACHABLE_DEFAULT)
>
> so, if i set a page attrubite is PAGE_READONLY, this attribute will set to
> pte , right? so ,
> why it should shift 6 bits?
 
Thanks a lot. I am puzzle that  if i set a page attrubite is PAGE_READONLY, tlb_write_indexed()
will write the 6 bits to entrylo0 register? i am using 24KEC soc.
 
Thanks,
Figo.zhang
 
>
> >
> > > D:
> > > V:
> > > G:
> > >
> > > and how the kernel write the this 6 bit to entrylo0/1 register?
> >
> > A TLB write instruction about 5 lines further down in the code.
> >
>
> which function write those 6 bits to register? tlb_write_indexed() ? if i
> want set pages cache attribute is uncached/write-back , how it can set it
> correctly to MIPS?

See drivers/char/mem.c; search for pgprot_noncached().  This is where
for uncached mmaps pick the apropriate page protection and cache bits.
Several other drivers may do equivalent things.

 Ralf

<Prev in Thread] Current Thread [Next in Thread>