From: Dave Jones <davej@codemonkey.org.uk>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Bryan Whitehead <driver@jpl.nasa.gov>,
Mark Cuss <mcuss@cdlsystems.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel reports 4 CPUS instead of 2...
Date: Thu, 17 Oct 2002 15:19:02 +0100 [thread overview]
Message-ID: <20021017141902.GB21222@suse.de> (raw)
In-Reply-To: <Pine.LNX.3.95.1021017085043.5202A-100000@chaos.analogic.com>
On Thu, Oct 17, 2002 at 08:56:15AM -0400, Richard B. Johnson wrote:
> > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
> ^____ hyperstuff
>
>
> Your CPU purports to "support" HT, but It doesn't "do" HT!
> Maybe somebody from Intel can explain, but I heard that they
> added the HT bit before they implimented hyper-threading.
> Anyways, maybe you can "turn something on" in the BIOS?
It's HT capable, but lacks the extra sibling found in the
more expensive models.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-10-17 14:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 17:24 Kernel reports 4 CPUS instead of 2 Mark Cuss
2002-10-16 17:35 ` Richard B. Johnson
2002-10-16 17:56 ` Samuel Flory
2002-10-16 17:54 ` Richard B. Johnson
2002-10-16 18:14 ` Samuel Flory
2002-10-16 19:28 ` James Cleverdon
2002-10-16 19:44 ` Mark Cuss
2002-10-16 20:10 ` Richard B. Johnson
2002-10-16 20:47 ` Samuel Flory
2002-10-16 21:44 ` Mark Mielke
2002-10-16 22:14 ` Samuel Flory
2002-10-16 22:21 ` Mark Cuss
2002-10-16 18:37 ` Mark Cuss
2002-10-16 23:21 ` Bryan Whitehead
2002-10-17 0:34 ` Mark Chernault
2002-10-17 12:56 ` Richard B. Johnson
2002-10-17 14:19 ` Dave Jones [this message]
2002-10-17 17:15 ` Bryan B Whitehead
2002-10-16 17:37 ` Joel Jaeggli
2002-10-16 17:48 ` Mark Cuss
2002-10-16 17:44 ` FD Cami
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 18:08 Nakajima, Jun
2002-10-17 1:02 Matt_Domsch
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=20021017141902.GB21222@suse.de \
--to=davej@codemonkey.org.uk \
--cc=driver@jpl.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=mcuss@cdlsystems.com \
--cc=root@chaos.analogic.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