mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Intel Core Duo/Duo2 T2300/E6400 - Hyper-Threading (the absence of)
Date: Mon, 8 Jan 2007 18:06:20 -0800	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKKEOGAMAC.davids@webmaster.com> (raw)
In-Reply-To: <20070108094432.GF5276@curie-int.orbis-terrarum.net>


> 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. That just means the CPU supports hyper-threading technology. That
doesn't mean it actually has an extra CPU per physical core, or that even if
it did, that that core was enabled.

> Both the Core1 and Core2 chips I have the ht bit set, but present only
> their two physical cores to the system. No access to the hyper-threading
> capabilities at all. I also see no configuration options in the BIOS to
> enable or disable hyper-threading. That is, /proc/cpuinfo and all
> topology data only shows 2 CPUs present, and that they are not the HT
> pair.
> (CONFIG_NR_CPUS=8 is set).

Intel considers multiple physical cores on a chip to be hyper-threading too.
HT is a marketing term, not a technical one.

> (This was originally triggered by somebody else's code that read the CPU
> flags, saw hyper-threading, and decided there were 2x cpus for each
> physical core. Said code has already been taken out back and shot
> repeatedly).

Yeah, that's wrong for many reasons. Even if the CPU does support an extra
logical core per physical core, it may or may not be enabled and in use.
Basically, the HT bit being set tells you that you should continue to
determine the number of logical and physical cores present. It's just a step
in the detection sequence.

DS



      parent reply	other threads:[~2007-01-09  2:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08  9:44 Robin H. Johnson
2007-01-08 10:01 ` Jakub Jelinek
2007-01-09  2:06 ` David Schwartz [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=MDEHLPKNGKAHNMBLJOLKKEOGAMAC.davids@webmaster.com \
    --to=davids@webmaster.com \
    --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

Powered by JetHome