public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: b_adlakha@softhome.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: HYPERTHREADING on older P4???
Date: Wed, 5 Feb 2003 13:07:07 +0000	[thread overview]
Message-ID: <20030205130707.GA616@codemonkey.org.uk> (raw)
In-Reply-To: <courier.3E410B73.000041C3@softhome.net>

On Wed, Feb 05, 2003 at 06:02:43AM -0700, b_adlakha@softhome.net wrote:
 > hi,
 > /proc/cpuinfo reports "ht" in the supported options...I have a p4 2 ghz 
 > stepping 4, and when I boot with an SMP kernel, it shows another thing :
 > siblings 1 
 > 
 > I think HT is there in all p4s, so can it be enabled in older P4s? Like 
 > mine? What does "siblings = 1" mean? 
 
It means there is one 'thread'. Ergo, you do not have the possibility
of running this as you would a true HT P4.  There are a limited number
of Northwood P4's out there which do support HT and have >1 sibling,
but asides from those, you'll need a Xeon to take advantage of it.

There are countless rumours of being able to enable extra siblings
by poking MSRs, but not one person has to my knowledge achieved this.
Some folks have also allegedly found that snipping pins or wiring extra
bits to them have enabled the 'extra sibling'. Whether this is true or
not, and whether it is 100% equivalent to a real HT part is again,
questionable.

	Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2003-02-05 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 13:02 HYPERTHREADING on older P4??? b_adlakha
2003-02-05 13:07 ` Dave Jones [this message]
2003-02-05 21:55   ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2003-02-05 17:43 Mikael Pettersson
2003-02-06 20:21 ` Bill Davidsen
2003-02-10 21:59 Margit Schubert-While
2003-02-11 11:42 ` b_adlakha
2003-02-11 15:03 ` Pawel Bernadowski

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=20030205130707.GA616@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=b_adlakha@softhome.net \
    --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