From: eugene@ns.armcci.am
To: Chris Snook <csnook@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ht CPU flag
Date: Sat, 19 May 2007 10:18:20 +0500 (AMST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705190858590.29910@ns.armcci.am> (raw)
In-Reply-To: <464E03C5.6040507@redhat.com>
On Fri, 18 May 2007, Chris Snook wrote:
> eugene@ns.armcci.am wrote:
>>
>>
>> On Fri, 18 May 2007, Chris Snook wrote:
>>
>> > eugene@ns.armcci.am wrote:
>> > > ---------------------------------------------------------------------------
>> > >
>> > >
>> > > I have Pentium D CPU, which many Windows utilities like cpuz, wcpuid,
>> > > everest identify as D 930 (Dual Core, 3GHz). From Intel site I find
>> > > out
>> > > that it has no HT feature, nor Windows XP identify it as HT.
>> > >
>> > > Why do I have "ht" flag in cpuinfo?
>> > > -----------------------------------
>> >
>> > The "ht" flag merely means "I know how to report hyperthreaded logical
>> > processors if I have them." My Woodcrest Xeon 5110 and my Athlon64 X2
>> > both have the "ht" flag, and correctly report the zero hyperthreaded
>> > logical processors they each have.
>> >
>> > -- Chris
>> >
>> >
>>
>> Thanks, Chris.
>>
>> Am I right that is chipset on mainboard, who is saying - "I know....", not
>> CPU itself? Is it better to switch off HT support in BIOS?
>> Is it possible to generate CPU name as: "Pentium D 930" in /proc/cpuinfo?
>> On the other server I have some 2GHz HT Xeons which can't be identified on
>> Intel site because of strange naming pattern.
>> I tried to find any utility for Linux to solve this, but it looks like
>> everybody are using /pros/cpuinfo, which is not enough :)
>>
>> Regards, Eugene.
>
> While the BIOS can disable HT, the ability to *report* HT or the lack thereof
> is within the CPU itself. I doubt my socket AM2 board has the faintest clue
> what HT is.
>
> As for human-readable names, the model name in /proc/cpuinfo comes from the
> processor name string, and includes however much or little information the
> vendor thinks the lay user wants to know. If you want more detail, you can
> always interpret the model, stepping, and other related fields to determine
> the model number.
>
> If you don't want to manually look up model info on a CPU version table,
> x86info and dmidecode will give you more information.
>
> -- Chris
>
As I already told, there is no stepping 4 for Xeons on Intel site! So
/proc/cpuinfo, dmidecode, x86info are all wrong.
Moreover, x86info is too old and can't work with /sys fs.
Also Linux is poor on giving FSB and Memory frequency, which I need to be
sure that memory timing is correct (SPD gives slower parameters then are
on SDRAM labels :( ).
next prev parent reply other threads:[~2007-05-19 5:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 16:47 eugene
2007-05-18 17:54 ` Bernd Eckenfels
2007-05-18 18:45 ` H. Peter Anvin
2007-05-18 19:07 ` Siddha, Suresh B
2007-05-18 19:45 ` Bernd Eckenfels
2007-05-18 19:17 ` Chris Snook
2007-05-18 19:33 ` eugene
2007-05-18 19:51 ` Chris Snook
2007-05-19 5:18 ` eugene [this message]
2007-05-19 6:18 ` H. Peter Anvin
2007-05-19 8:33 ` eugene
2007-05-19 16:38 ` Bernd Eckenfels
2007-05-19 18:11 ` H. Peter Anvin
2007-05-19 12:13 ` eugene
2007-05-19 16:41 ` Bernd Eckenfels
2007-05-18 20:32 ` Bernd Eckenfels
2007-05-18 23:20 ` H. Peter Anvin
2007-05-19 21:07 ` eugene
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=Pine.LNX.4.64.0705190858590.29910@ns.armcci.am \
--to=eugene@ns.armcci.am \
--cc=csnook@redhat.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
all inboxes | Powered by JetHome®