From: Dave Jones <davej@codemonkey.org.uk>
To: Scott Robert Ladd <scott@coyotegulch.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel for Pentium 4 hyperthreading?
Date: Sun, 15 Dec 2002 13:44:08 +0000 [thread overview]
Message-ID: <20021215134408.GA20335@suse.de> (raw)
In-Reply-To: <FKEAJLBKJCGBDJJIPJLJMEGPDLAA.scott@coyotegulch.com>
On Sat, Dec 14, 2002 at 08:11:45PM -0500, Scott Robert Ladd wrote:
> I've just received a new computer based on a 2.8 GHz Pentium 4 with
> hyper-threading enabled. Yes, HT is enabled in the BIOS; yes, /proc/cpuinfo
> shows the 'ht' flag; yes, I've compiled 2.4.20 (stock) with SMP and ACPI
> enabled.
> No, it doesn't work. cat /proc/cpuinfo reports a single CPU.
Note that just because /proc/cpuinfo shows 'ht' does not mean you can
use it in hyperthreaded mode. To do that, you also have to have >1
sibling in the physical package. Non-Xeon type P4's don't have the
extra sibling, so don't function as a hyperthreaded CPU.
> Can 2.4.20 handle a Pentium 4 (not Xeon, mind you) with HT? What could I be
> missing in my kernel build?
It's more a case of whats missing in your CPU package 8-)
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-12-15 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 0:52 Linux-2.4.20: bug with radeonfb José Luis Tallón
2002-12-15 0:56 ` Adrian Bunk
2002-12-15 1:11 ` Kernel for Pentium 4 hyperthreading? Scott Robert Ladd
2002-12-15 13:44 ` Dave Jones [this message]
2002-12-15 15:07 ` Scott Robert Ladd
2002-12-15 15:47 ` Vergoz Michael (SYSDOOR)
2002-12-15 15:58 ` Dave Jones
2002-12-17 19:39 ` Bill Davidsen
2002-12-15 15:57 ` Dave Jones
2002-12-15 17:40 ` Scott Robert Ladd
2002-12-15 19:17 ` Dave Jones
2002-12-15 11:55 ` Linux-2.4.20: bug with radeonfb - solved José Luis Tallón
2002-12-15 16:19 ` Adrian Bunk
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=20021215134408.GA20335@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@coyotegulch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.