From: Jakub Jelinek <jakub@redhat.com>
To: linux-kernel@vger.kernel.org, robbat2@gentoo.org
Subject: Re: Intel Core Duo/Duo2 T2300/E6400 - Hyper-Threading (the absence of)
Date: Mon, 8 Jan 2007 05:01:51 -0500 [thread overview]
Message-ID: <20070108100151.GK29911@devserv.devel.redhat.com> (raw)
In-Reply-To: <20070108094432.GF5276@curie-int.orbis-terrarum.net>
On Mon, Jan 08, 2007 at 01:44:32AM -0800, Robin H. Johnson wrote:
> (Please CC me, I am not subscribed to LKML [I have set the
> Mail-Followup-To header accordingly]).
>
> On two of my new machines, with Intel Core Duo T2300 and Core2 Duo E6400
> chips respectively, I noticed some weirdness in how many CPUs are
> present.
>
> If the hyper-threading bit is present in the CPU info, should there
> always be a an extra CPU presented to the system per physical core?
No. The ht flag just says whether HT reporting via CPUID is supported.
Core2 Duo E6400 is AFAIK not hyper-threaded, you just have 2 real sibling
CPUs (except that they share L2 cache).
Jakub
next prev parent reply other threads:[~2007-01-08 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 9:44 Intel Core Duo/Duo2 T2300/E6400 - Hyper-Threading (the absence of) Robin H. Johnson
2007-01-08 10:01 ` Jakub Jelinek [this message]
2007-01-09 2:06 ` David Schwartz
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=20070108100151.GK29911@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robbat2@gentoo.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