From: "David L. DeGeorge" <dld@degeorge.org>
To: linux-kernel@vger.kernel.org
Subject: Re: CPU/cache detection wrong
Date: Mon, 30 Sep 2002 21:06:10 -0400 [thread overview]
Message-ID: <200209302106.10518.dld@degeorge.org> (raw)
I too have incorrect CPU/cache detection using 2.4.20-pre7-ac3. I seem to
recall it working correctly on 2.4.19-ac1 (this was the version in which the
ac did not get added by the patch). Anyway I have a tualatin PIII with a 512K
L2 cache. I inserted the printk in setup.c that Alan asked for earlier in
the thread and got three outputs (it's a two processor machine). I have
edited everything but the printk output and the CPU:... lines. Things are
working fine with the kernel command line cachesize=512.
David
Sep 30 12:56:02 janus kernel: Cache info byte: 01
Sep 30 12:56:02 janus kernel: Cache info byte: 02
Sep 30 12:56:02 janus kernel: Cache info byte: 03
Sep 30 12:56:02 janus kernel: Cache info byte: 00
Sep 30 12:56:02 janus kernel: Cache info byte: 00
Sep 30 12:56:02 janus last message repeated 6 times
Sep 30 12:56:02 janus kernel: Cache info byte: 83
Sep 30 12:56:02 janus kernel: Cache info byte: 08
Sep 30 12:56:02 janus kernel: Cache info byte: 04
Sep 30 12:56:02 janus kernel: Cache info byte: 0C
Sep 30 12:56:02 janus kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
Sep 30 12:56:02 janus kernel: CPU: L2 cache: 256K
...........................................................
Sep 30 12:56:02 janus kernel: Cache info byte: 01
Sep 30 12:56:02 janus kernel: Cache info byte: 02
Sep 30 12:56:02 janus kernel: Cache info byte: 03
Sep 30 12:56:02 janus kernel: Cache info byte: 00
Sep 30 12:56:02 janus last message repeated 7 times
Sep 30 12:56:02 janus kernel: Cache info byte: 83
Sep 30 12:56:02 janus kernel: Cache info byte: 08
Sep 30 12:56:02 janus kernel: Cache info byte: 04
Sep 30 12:56:02 janus kernel: Cache info byte: 0C
Sep 30 12:56:02 janus kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
Sep 30 12:56:02 janus kernel: CPU: L2 cache: 256K
.....................................................................................
Sep 30 12:56:02 janus kernel: Cache info byte: 01
Sep 30 12:56:02 janus kernel: Cache info byte: 02
Sep 30 12:56:02 janus kernel: Cache info byte: 03
Sep 30 12:56:02 janus kernel: Cache info byte: 00
Sep 30 12:56:02 janus last message repeated 7 times
Sep 30 12:56:02 janus kernel: Cache info byte: 83
Sep 30 12:56:02 janus kernel: Cache info byte: 08
Sep 30 12:56:02 janus kernel: Cache info byte: 04
Sep 30 12:56:02 janus kernel: Cache info byte: 0C
Sep 30 12:56:02 janus kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
Sep 30 12:56:02 janus kernel: CPU: L2 cache: 256K
next reply other threads:[~2002-10-01 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 1:06 David L. DeGeorge [this message]
2002-10-01 11:18 ` CPU/cache detection wrong Dave Jones
2002-10-01 13:35 ` Maciej W. Rozycki
2002-10-01 15:15 ` Dave Jones
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=200209302106.10518.dld@degeorge.org \
--to=dld@degeorge.org \
--cc=linux-kernel@vger.kernel.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 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.