From: Dave Jones <davej@codemonkey.org.uk>
To: Alexander Hoogerhuis <alexh@ihatent.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: CPU/cache detection wrong
Date: Tue, 1 Oct 2002 12:06:28 +0100 [thread overview]
Message-ID: <20021001110628.GA17865@suse.de> (raw)
In-Reply-To: <m3smzqipzd.fsf@lapper.ihatent.com>
On Tue, Oct 01, 2002 at 09:21:26AM +0200, Alexander Hoogerhuis wrote:
> Dave Jones <davej@codemonkey.org.uk> writes:
>
> > On Mon, Sep 30, 2002 at 07:43:16PM +0200, Alexander Hoogerhuis wrote:
> >
> > > PU: Before vendor init, caps: 3febf9ff 00000000 00000000, vendor = 0
> > > Cache info byte: 50
> >
> > Instruction TLB (ignored)
> >
> > > Cache info byte: 5B
> >
> > Data TLB (ignored)
> >
> > > Cache info byte: 66
> >
> > 8K L1 data cache
> >
> > > Cache info byte: 00
> > > Cache info byte: 00
> > > Cache info byte: 00
> > > Cache info byte: 00
> > > Cache info byte: 00
> > > Cache info byte: 00
> > > Cache info byte: 00
> > > Cache info byte: 00
> >
> > Null
> >
> > > Cache info byte: 40
> >
> > No 3rd level cache.
> >
> > > Cache info byte: 70
> >
> > 12K-uops trace cache
> >
> > > Cache info byte: 7B
> >
> > 512K L2 cache
> >
> > > Cache info byte: 00
> >
> > Null.
> >
> > > CPU: L1 I cache: 0K, L1 D cache: 8K
> > > CPU: L2 cache: 512K
> >
>
> Here we go:
>
> CPU: Trace cache: 12K uops, L1 D cache: 8K
> CPU: L2 cache: 512K
>
> But my BIOS still say I should have 8Kb/8Kb I/D L1 cache... oh
> well. I'm sure Alan Cox would just write it up as marketing, since
> thats about how reliable a BIOS is :)
Hmm, can a P4 have a trace cache AND an L1 I cache ?
I thought they were exclusive, which is why the code
doesn't take this into account. Easily fixed if so though..
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-10-01 10:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 12:29 CPU/cache detection wrong 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 [this message]
2002-10-01 15:31 ` Alexander Hoogerhuis
2002-10-01 17:01 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 1:06 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
2002-10-01 16:03 ` Maciej W. Rozycki
2002-10-01 16:31 ` Dave Jones
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=20021001110628.GA17865@suse.de \
--to=davej@codemonkey.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alexh@ihatent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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.