From: Ralf Baechle <ralf@linux-mips.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: lovecentry <lovecentry@gmail.com>, linux-mips@linux-mips.org
Subject: Re: kseg1 uncache access issue
Date: Tue, 8 Jan 2008 18:59:03 +0000 [thread overview]
Message-ID: <20080108185903.GC30643@linux-mips.org> (raw)
In-Reply-To: <20080108170206.GA8777@alpha.franken.de>
On Tue, Jan 08, 2008 at 06:02:06PM +0100, Thomas Bogendoerfer wrote:
> On Wed, Jan 09, 2008 at 12:35:06AM +0800, lovecentry wrote:
> > As we know in mips achitecture if current pc falls into kseg1 segment, any
> > memory reference will bypass cache and fetch directly from dram. But for
> > some prcoessor such like mips R10K it has off chip L2 cache. I haven't found
>
> why do you think so ? R10k L2 cache controller is inside CPU and any
> access with uncached attribute will go directly to memory. The only
> systems, where this might be different are systems with caches unknown
> to the cpu. But even those usually obey that uncached accesses are
> going directly to memory.
It should also be mentioned that some R10000 machines do odd stuff with
uncached addresses.
IP27 class machines reuse the entire physical address space several times
to map different things. The selection of the four uncached address
spaces id done by the uncached attribute which is specified either in
the TLB or or as as bit 59..60 of a virtual address in XKPHYS.
The memory controller of the Indigo 2 R10000 needs to be switched to a
special slower mode to allow uncached accesses first.
Ralf
next prev parent reply other threads:[~2008-01-08 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:35 kseg1 uncache access issue lovecentry
2008-01-08 16:35 ` lovecentry
2008-01-08 17:02 ` Thomas Bogendoerfer
2008-01-08 18:59 ` Ralf Baechle [this message]
2008-01-09 13:20 ` 答复: " lovecentry
2008-01-09 13:20 ` lovecentry
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=20080108185903.GC30643@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=lovecentry@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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.