Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Keith M Wesolowski <wesolows@foobazco.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: RFC: Cleanup/detection patch
Date: Thu, 05 Apr 2001 14:53:14 -0700	[thread overview]
Message-ID: <3ACCE94A.A551470D@mvista.com> (raw)
In-Reply-To: 20010405140338.A1508@foobazco.org

Keith M Wesolowski wrote:
> 
> On Thu, Apr 05, 2001 at 01:29:13PM -0700, Jun Sun wrote:
> 
> > I don't like bc_ops idea.  Usually the external cache capability is still
> > integral part of the CPU.
> 
> How can it be both an integral part of the CPU and board-specific?

Hmm, I am thinking about something like Rm7k, where the tertiary cache is
controlled by the CPU (through cache instruction and TagLo/TagHi regsiters,
etc) but the size is only known to the board.

I think some CPUs can have secondary, external cache but cannot figure the
size and, especially, the layout (# of ways, ...) automatically.  (Any
confirmation?)

Those are what I was referring to.

The key point is that machine_detection() should happen BEFORE
cpu_probe()/cache_probe() so that we have an elegant way to address the above
situation.

Jun

  reply	other threads:[~2001-04-05 21:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02  6:52 RFC: Cleanup/detection patch Keith M Wesolowski
2001-04-04  2:43 ` Jun Sun
2001-04-04  3:30   ` Keith M Wesolowski
2001-04-04 17:54     ` Jun Sun
2001-04-05  7:46       ` Keith M Wesolowski
2001-04-05 20:29         ` Jun Sun
2001-04-05 21:03           ` Keith M Wesolowski
2001-04-05 21:53             ` Jun Sun [this message]
2001-04-09  6:40         ` Geert Uytterhoeven

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=3ACCE94A.A551470D@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=wesolows@foobazco.org \
    /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