From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Discrepancies between /proc/cpuinfo and Dave J's x86info
Date: 10 Jul 2001 21:27:33 -0700 [thread overview]
Message-ID: <9igkjl$nk1$1@cesium.transmeta.com> (raw)
In-Reply-To: <3B4BC5C0.BDDC12A6@home.com>
Followup to: <3B4BC5C0.BDDC12A6@home.com>
By author: Jordan <ledzep37@home.com>
In newsgroup: linux.dev.kernel
>
> According to Dave J's utility the cpu's appear to be exactly the same
> just as the Intel boxes said when I bought them. What might be causing
> these values to be different. And if the BIOS is setting things up
> incorrectly then why does Dave J's utility show the correct values?
> Thanks for any help.
>
/proc/cpuinfo shows "cooked" values which may be modified by the
kernel, depending on what it knows about CPU errata or kernel
capabilities.
-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
next prev parent reply other threads:[~2001-07-11 4:27 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 [this message]
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 ` [PATCH] Re: Discrepancies between /proc/cpuinfo and Dave J's x86info H. Peter Anvin
2001-07-11 16:29 ` 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='9igkjl$nk1$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;
as well as URLs for NNTP newsgroup(s).