From: Jun Sun <jsun@mvista.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: CONFIG_MIPS_UNCACHED
Date: Sun, 24 Jun 2001 21:42:32 -0700 [thread overview]
Message-ID: <20010624214232.A18389@mvista.com> (raw)
In-Reply-To: <020c01c0fc21$51256760$0deca8c0@Ulysses>; from kevink@mips.com on Sat, Jun 23, 2001 at 10:15:49PM +0200
On Sat, Jun 23, 2001 at 10:15:49PM +0200, Kevin D. Kissell wrote:
> > > Since the kernel cache attribute is never initialized before
> > > ld_mmu_{whatever} is invoked, and since that Config field
> > > does not have a well-defined reset state on many MIPS
> > > CPUs, it would appear that we are in effect trusting the
> > > bootloader to have done something reasonable like
> > > set kseg0 to be non-cachable or write-through, either
> > > of which would be safe for the current code.
> >
> > I think you just proposed a fix: check current config register when we
> turn
> > off cache. Thanks. :-)
>
> That's a heuristic at best. If the config register comes up random,
> it can appear to be sane even though the cache is in fact uninitialized.
>
For any practical reasons, we can assume there is a loader for Linux,
and we can assume loader does not run with a random config register.
Jun
next prev parent reply other threads:[~2001-06-25 4:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 16:05 CONFIG_MIPS_UNCACHED Jun Sun
2001-06-23 17:17 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-23 17:17 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-23 17:49 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-06-23 20:15 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-23 20:15 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-25 4:42 ` Jun Sun [this message]
2001-06-25 6:51 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-25 6:51 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-25 16:38 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-06-25 17:35 ` CONFIG_MIPS_UNCACHED Justin Carlson
2001-06-26 8:50 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-26 8:50 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-26 13:11 ` CONFIG_MIPS_UNCACHED Maciej W. Rozycki
2001-06-25 13:22 ` CONFIG_MIPS_UNCACHED Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-01-23 23:26 CONFIG_MIPS_UNCACHED Quinn Jensen
2001-01-23 23:53 ` CONFIG_MIPS_UNCACHED Pete Popov
2001-01-24 20:10 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-01-25 0:31 ` CONFIG_MIPS_UNCACHED Ralf Baechle
2001-01-25 1:09 ` CONFIG_MIPS_UNCACHED Pete Popov
2001-01-25 1:37 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-01-26 10:02 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-01-26 10:02 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
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=20010624214232.A18389@mvista.com \
--to=jsun@mvista.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox