public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: Discrepancies between /proc/cpuinfo and Dave J's  x86info
Date: 9 Oct 2001 18:38:39 -0700	[thread overview]
Message-ID: <9q08qv$v7$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0107111625410.1811-100000@Appserv.suse.de> <p05100361b77232f67994@[207.213.214.37]>

Followup to:  <p05100361b77232f67994@[207.213.214.37]>
By author:    Jonathan Lundell <jlundell@pobox.com>
In newsgroup: linux.dev.kernel
>
> At 4:28 PM +0200 2001-07-11, Dave Jones wrote:
> >On Wed, 11 Jul 2001, Hugh Dickins wrote:
> >
> >>  Am I paranoid?
> >
> >Probably :)
> >The Intel CPUs with PSN I've seen simply drop 1 level.
> >What other CPUs support this feature? ISTR Transmeta had it?
> >Do they behave the same?
> >
> >>   I feel nervous about "c->cpuid_level--" inferring
> >>  what we expect to happen to it, would prefer to check it (below).
> >>  +		c->cpuid_level = cpuid_eax(0);
> >
> >No biggie, either solution is fine with me.
> 
> HD's version has the advantage of not having to make assumptions 
> about how future CPUs might handle the level, and leaves open the 
> alternative possibility of leaving the level at 3 (or some future 4) 
> and just turning off the serial-number capability.
> 

cpuid_level-- is wrong on at least one existing processor (Crusoe),
which doesn't have CPUID level 2 and therefore goes from 3 to 1.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  parent reply	other threads:[~2001-10-10  1:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11  3:19 Discrepancies between /proc/cpuinfo and Dave J's x86info Jordan
2001-07-11  4:27 ` H. Peter Anvin
2001-07-11  4:37   ` Jonathan Lundell
2001-07-11  4:44     ` H. Peter Anvin
2001-07-11  5:04       ` Jonathan Lundell
2001-07-11 11:00 ` Dave Jones
2001-07-11 12:03 ` Hugh Dickins
2001-07-11 12:23   ` Dave Jones
2001-07-11 14:09     ` [PATCH] " Hugh Dickins
2001-07-11 14:28       ` Dave Jones
2001-07-11 16:47         ` Jonathan Lundell
2001-07-11 17:00           ` Dave Jones
2001-07-12  6:58             ` [PATCH] Re: Discrepancies between /proc/cpuinfo and Dave J's x86i Kai Henningsen
2001-10-10  1:38           ` H. Peter Anvin [this message]
2001-07-11 16:29       ` [PATCH] Re: Discrepancies between /proc/cpuinfo and Dave J's x86info Linus Torvalds
2001-07-11 15:51     ` Jordan Breeding

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='9q08qv$v7$1@cesium.transmeta.com' \
    --to=hpa@zytor.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