From: Andi Kleen <andi@firstfloor.org>
To: VUB Stefan Seidel <sseidel@vub.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Not all logical processors activated on Dual Core Xeon (== no Hyperthreading)
Date: Wed, 09 Jan 2008 16:25:50 +0100 [thread overview]
Message-ID: <p73odbvowap.fsf@bingen.suse.de> (raw)
In-Reply-To: <47849240.3040305@vub.de> (VUB Stefan Seidel's message of "Wed\, 09 Jan 2008 10\:22\:08 +0100")
VUB Stefan Seidel <sseidel@vub.de> writes:
> I have the following system here: two dual-core Xeon 5130 on an Intel
> S5000V-SA motherboard. The kernel detects 4 CPUs, from what I learn
> through /proc/cpuinfo, these are the 4 cores (two per
> package). However, I think it should be 8 logical processors, because
> the Xeons should be able to do Hyperthreading (or
Core2 Duo based Xeons do not support Hyper Threading.
> ===========================
> but acpidump shows 8 CPUs in multiple locations:
That's likely because the BIOS supports Quad Core CPUs, but does
not disable the excessive objects if you only plug in Dual Core
-Andi
prev parent reply other threads:[~2008-01-09 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 9:22 Not all logical processors activated on Dual Core Xeon (== no Hyperthreading) VUB Stefan Seidel
2008-01-09 15:25 ` Andi Kleen [this message]
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=p73odbvowap.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sseidel@vub.de \
/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