public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Dave Jones <davej@suse.de>
Cc: Steven Walter <srwalter@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: [Patch] Output of L1,L2 and L3 cache sizes to /proc/cpuinfo
Date: Tue, 22 May 2001 06:44:30 +0200	[thread overview]
Message-ID: <20010522064430.D4934@khan.acc.umu.se> (raw)
In-Reply-To: <20010521215927.B31289@hapablap.dyn.dhs.org> <Pine.LNX.4.30.0105220519160.20545-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.30.0105220519160.20545-100000@Appserv.suse.de>; from davej@suse.de on Tue, May 22, 2001 at 05:22:35AM +0200

On Tue, May 22, 2001 at 05:22:35AM +0200, Dave Jones wrote:
> On Mon, 21 May 2001, Steven Walter wrote:
> 
> > > Any particular reason this needs to be done in the kernel, as opposed
> > > to having your script read /dev/cpu/*/cpuid?
> > Wouldn't that be the same reason we have /anything/ in cpuinfo?
> 
> When /proc/cpuinfo was added, we didn't have /dev/cpu/*/cpuid
> Now that we do, we're stuck with keeping /proc/cpuinfo for
> compatability reasons.

AFAIK, not all processors support cpuid.


/david
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-05-22  4:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21 12:39 [Patch] Output of L1,L2 and L3 cache sizes to /proc/cpuinfo 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-05-22  8:52 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
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

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=20010522064430.D4934@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srwalter@yahoo.com \
    /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