All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Knoblauch <martin.knoblauch@teraport.de>
To: "H. Peter Anvin" <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: Wed, 23 May 2001 01:57:47 +0200	[thread overview]
Message-ID: <3B0AFCFB.CAE7A145@teraport.de> (raw)
In-Reply-To: <3B0A28C0.2FFFC935@TeraPort.de> <3B0A3794.15BDF9D6@TeraPort.de> <3B0A99E7.467CE534@transmeta.com>

"H. Peter Anvin" wrote:
> 
> "Martin.Knoblauch" wrote:
> >
> >  After some checking, I could have made the answer a bit less terse:
> >
> > - it would require that the kernel is compiled with cpuid [module]
> > support
> >   - not everybody may want enable this, just for getting one or two
> >     harmless numbers.
> 
> If so, then that's their problem.  We're not here to solve the problem of
> stupid system administrators.
>

 They may not be stupid, just mislead :-( When Intel created the "cpuid"
Feature some way along the P3 line, they gave a stupid reason for it and
created a big public uproar. As silly as I think that was (on both
sides), the term "cpuid" is tainted. Some people just fear it like hell.
Anyway.
 
> > - you would need a utility with root permission to analyze the cpuid
> > info. The
> >   cahce info does not seem to be there in clear ascii.
> 
> Bullsh*t.  /dev/cpu/%d/cpuid is supposed to be mode 444 (world readable.)
> 

 Thanks you :-) In any case, on my system (Suse 7.1) the files are mode
400.

Martin

  parent reply	other threads:[~2001-05-22 23:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22  8:52 [Patch] Output of L1,L2 and L3 cache sizes to /proc/cpuinfo Martin.Knoblauch
2001-05-22  9:55 ` Martin.Knoblauch
2001-05-22 16:55   ` H. Peter Anvin
2001-05-22 18:08     ` Alan Cox
2001-05-22 23:57     ` Martin Knoblauch [this message]
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=3B0AFCFB.CAE7A145@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 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.