From: James Cleverdon <jamesclv@us.ibm.com>
To: Guido Arenstedt <ga200@doc.ic.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: Hyperthreading in -ac series
Date: Fri, 20 Sep 2002 15:47:59 -0700 [thread overview]
Message-ID: <200209201547.59508.jamesclv@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.42.0209202323530.23572-100000@faya.doc.ic.ac.uk>
On Friday 20 September 2002 03:36 pm, Guido Arenstedt wrote:
> Hyperthreading does not seem to work in the -ac series
> it works fine with a stock 2.4.19 kernel
>
> during bootup i only get the message:
> WARNING: No sibling found for CPU 0.
> WARNING: No sibling found for CPU 1.
>
> or is this done on purpose?
The latter. Hyperthreading _is_ working in the kernel, but it is not finding
"sibling" CPUs to match the real ones. (Or, as we prefer to call them,
DiVitos to match the Schwartzenegers. ;^)
Check your BIOS. Some turn off hyperthreading by default. (Notably, IBM's
x440....)
--
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com
next prev parent reply other threads:[~2002-09-20 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 22:36 Hyperthreading in -ac series Guido Arenstedt
2002-09-20 22:47 ` James Cleverdon [this message]
2002-09-21 21:54 ` Guido Arenstedt
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=200209201547.59508.jamesclv@us.ibm.com \
--to=jamesclv@us.ibm.com \
--cc=ga200@doc.ic.ac.uk \
--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