public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin.Knoblauch" <Martin.Knoblauch@TeraPort.de>
To: hpa@transmeta.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Output of L1,L2 and L3 cache sizes to /proc/cpuinfo
Date: Tue, 22 May 2001 10:52:16 +0200	[thread overview]
Message-ID: <3B0A28C0.2FFFC935@TeraPort.de> (raw)

>> 
>> Hi, 
>> 
>> while trying to enhance a small hardware inventory script, I found that 
>> cpuinfo is missing the details of L1, L2 and L3 size, although they may 
>> be available at boot time. One could of cource grep them from "dmesg" 
>> output, but that may scroll away on long lived systems. 
>> 
>
>Any particular reason this needs to be done in the kernel, as opposed 
>to having your script read /dev/cpu/*/cpuid? 
>
>        -hpa 

 terse answer: probably the same reason as for most stuff in
/proc/cpuinfo :-)

 Seriously, is there any kind of documentation on for the stuff you
mention? I am willing to learn. Isn't the cpuid just a kind of
serialnumber? The one that caused the big flame wars when Intel
introduced the concept? In any case, on my system(s) there seems to be
no device behind those files. On some systems, there is even no
"/dev/cpu" directory.

 I agree in a way that the changes to processor.h are not neccessary -
unless other parts of the kernel are interested in those values. I
probably should change that to make the thing easier to digest.

Martin

             reply	other threads:[~2001-05-22  8:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22  8:52 Martin.Knoblauch [this message]
2001-05-22  9:55 ` [Patch] Output of L1,L2 and L3 cache sizes to /proc/cpuinfo Martin.Knoblauch
2001-05-22 16:55   ` H. Peter Anvin
2001-05-22 18:08     ` Alan Cox
2001-05-22 23:57     ` Martin Knoblauch
2001-05-23  0:05       ` H. Peter Anvin
2001-05-23  0:18         ` Tomas Telensky
2001-05-23  1:08           ` Dave Jones
2001-05-23  9:24             ` Martin.Knoblauch
2001-05-23  1:48       ` Dave Jones
2001-05-23  7:10         ` Martin.Knoblauch
2001-05-22 16:52 ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2001-05-21 12:39 Martin.Knoblauch
2001-05-21 15:16 ` H. Peter Anvin
2001-05-22  2:59   ` Steven Walter
2001-05-22  3:22     ` Dave Jones
2001-05-22  4:44       ` David Weinehall
2001-05-22 11:15         ` Dave Jones
2001-05-22 22:47   ` Tomas Telensky
2001-05-22 23:43     ` Dave Jones
2001-05-22 23:50     ` Martin Knoblauch

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=3B0A28C0.2FFFC935@TeraPort.de \
    --to=martin.knoblauch@teraport.de \
    --cc=hpa@transmeta.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox