public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Steffen Persvold <sp@scali.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG?] Xeon with HyperThreading and linux-2.4.20-rc2
Date: Wed, 20 Nov 2002 08:04:22 -0500	[thread overview]
Message-ID: <20021120080422.A1498@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211201236480.1139-100000@localhost.localdomain>; from hugh@veritas.com on Wed, Nov 20, 2002 at 12:53:04PM +0000

On Wed, Nov 20, 2002 at 12:53:04PM +0000, Hugh Dickins wrote:
> 
> I know too little to comment definitively, but it's my understanding
> that a dual HT machine should only show 2 processors in its MP table,
> their siblings only appearing through analysis of the ACPI tables.
> 
> Whether it's that your MP table has been wrongly set up, or that
> you've really been given 4 processors when you only asked for 2
> (sue your supplier!), I cannot say.  I've copied Jun at Intel
> and Arjan at RedHat, and hope they can shed more light on this.

Linux has zero problem with a sane MP table that lists all
CPU's. Intel normally seems to recommend against it (maybe N3.51 doesn't
like it or so) but it's all fair as far as I'm concerned.
The bios is supposed to offer you a choice
to disable hyperthreading, use that ;)

Greetings,
   Arjan van de Ven


-- 
But when you distribute the same sections as part of a whole which is a work 
based on the Program, the distribution of the whole must be on the terms of 
this License, whose permissions for other licensees extend to the entire whole,
and thus to each and every part regardless of who wrote it. [sect.2 GPL]

  reply	other threads:[~2002-11-20 12:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 18:03 Every semaphore call results in "uninterruptable sleep" Manfred Spraul
2002-11-16 13:26 ` Xeon with HyperThreading and linux-2.4.20-rc2 Steffen Persvold
2002-11-19 21:09   ` [BUG?] " Steffen Persvold
2002-11-19 21:42     ` Hugh Dickins
2002-11-20  9:56       ` Steffen Persvold
2002-11-20 12:53         ` Hugh Dickins
2002-11-20 13:04           ` Arjan van de Ven [this message]
2002-11-20 13:27             ` Steffen Persvold
2002-11-20 13:26               ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20 15:50 Nakajima, Jun
2002-11-20 16:00 ` Steffen Persvold
2002-11-20 16:55   ` Alan Cox

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=20021120080422.A1498@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=hugh@veritas.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sp@scali.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