public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "David L. DeGeorge" <dld@degeorge.org>, linux-kernel@vger.kernel.org
Subject: Re: CPU/cache detection wrong
Date: Tue, 1 Oct 2002 16:15:25 +0100	[thread overview]
Message-ID: <20021001151525.GA32467@suse.de> (raw)
In-Reply-To: <Pine.GSO.3.96.1021001153347.13606C-100000@delta.ds2.pg.gda.pl>

On Tue, Oct 01, 2002 at 03:35:54PM +0200, Maciej W. Rozycki wrote:


 > > Some of the tualatins have an errata which makes L2 cache sizing
 > > impossible. They actually report they have 0K L2 cache. By checking
 > > the CPU model, we can guess we have at least 256K (which is where Linux
 > > got that number from in your case). But this however means the 512K
 > > models will report as 256K too.
 > > To work around it, boot with cachesize=512 and all will be good.
 > 
 >  Strange -- why not to default to 256K and override it with the value
 > obtained from a cache descriptor if != 0, then?

Because the cache descriptor IS zero. So we default to 256K.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk

  reply	other threads:[~2002-10-01 15:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  1:06 CPU/cache detection wrong David L. DeGeorge
2002-10-01 11:18 ` Dave Jones
2002-10-01 13:35   ` Maciej W. Rozycki
2002-10-01 15:15     ` Dave Jones [this message]
2002-10-01 16:03       ` Maciej W. Rozycki
2002-10-01 16:31         ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2002-09-28 12:29 Alexander Hoogerhuis
2002-09-30 16:34 ` Alan Cox
2002-09-30 17:43   ` Alexander Hoogerhuis
2002-09-30 22:15     ` Dave Jones
2002-10-01  7:21       ` Alexander Hoogerhuis
2002-10-01 11:06         ` Dave Jones
2002-10-01 15:31           ` Alexander Hoogerhuis
2002-10-01 17:01             ` Vojtech Pavlik

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=20021001151525.GA32467@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=dld@degeorge.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    /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