public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Martin Knoblauch <martin.knoblauch@teraport.de>
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 17:05:28 -0700	[thread overview]
Message-ID: <3B0AFEC8.CDBF6C92@transmeta.com> (raw)
In-Reply-To: <3B0A28C0.2FFFC935@TeraPort.de> <3B0A3794.15BDF9D6@TeraPort.de> <3B0A99E7.467CE534@transmeta.com> <3B0AFCFB.CAE7A145@teraport.de>

Martin Knoblauch wrote:
> >
> > 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.
> 

Ummm... CPUID has been around since the P5, and even if you have one with
the serial-number feature, Linux disables it. 

> > > - 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.
> 

It's pointless since you can execute CPUID directly in user space.  The
device is there just to support CPU selection in a multiprocessor system.

	-hpa

  reply	other threads:[~2001-05-23  0:06 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
2001-05-23  0:05       ` H. Peter Anvin [this message]
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=3B0AFEC8.CDBF6C92@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.knoblauch@teraport.de \
    /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