From: Arjan van de Ven <arjanv@redhat.com>
To: Steffen Persvold <sp@scali.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
Hugh Dickins <hugh@veritas.com>,
Jun Nakajima <jun.nakajima@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG?] Xeon with HyperThreading and linux-2.4.20-rc2
Date: Wed, 20 Nov 2002 08:26:35 -0500 [thread overview]
Message-ID: <20021120082635.C1498@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211201417000.13800-100000@sp-laptop.isdn.scali.no>; from sp@scali.com on Wed, Nov 20, 2002 at 02:27:20PM +0100
On Wed, Nov 20, 2002 at 02:27:20PM +0100, Steffen Persvold wrote:
>
> Sure, the bios has this option (and it works). I just believed the 'noht'
> option would disable it from a kernel perspective. I understand that if
> the MP table lists 4 processors, the kernel must think it is 4 processors
> and enable them. But what is the purpose of the 'noht' option ? If it is
> to avoid scanning the ACPI table for CPUs, wouldn't it be less confusing
> to call it something like 'acpismp=disable', since you apparently can't
> disable the siblings anyway (when they are also listed in the MP table) ?
in theory we can, at least with the O(1) scheduling infrastructure
it's easy. it's just that nobody cared enough so far to do it
next prev parent reply other threads:[~2002-11-20 13:19 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
2002-11-20 13:27 ` Steffen Persvold
2002-11-20 13:26 ` Arjan van de Ven [this message]
-- 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=20021120082635.C1498@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