From: Valdis.Kletnieks@vt.edu
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Lin Ming <ming.m.lin@intel.com>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/7] perf: Check if HT is supported and enabled
Date: Tue, 04 Jan 2011 13:55:27 -0500 [thread overview]
Message-ID: <14831.1294167327@localhost> (raw)
In-Reply-To: Your message of "Tue, 04 Jan 2011 12:10:19 +0100." <1294139419.2016.115.camel@laptop>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
On Tue, 04 Jan 2011 12:10:19 +0100, Peter Zijlstra said:
> X86_FEATURE_HT tells us the CPU supports telling us about HT,
> smp_num_siblings > 1 tells us the CPU is capable of HT.
A subtle but important distinction. Several laptops ago, I had a P4-M chip that
had FEATURE_HT, but num_siblings == 1. ISTR trying to boot an SMP kernel on it
and it dying gloriously trying to bring up the non-existent other sibling.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2011-01-04 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 15:36 [PATCH 4/7] perf: Check if HT is supported and enabled Lin Ming
[not found] ` <AANLkTimp9VgD4qhOVmq-k1Ckzti9eeV8pf6Jvt5YB6nx@mail.gmail.com>
2010-12-28 8:51 ` Lin Ming
2011-01-03 10:58 ` Peter Zijlstra
2011-01-03 15:21 ` Andi Kleen
2011-01-03 19:53 ` H. Peter Anvin
2011-01-04 11:10 ` Peter Zijlstra
2011-01-04 13:38 ` Stephane Eranian
2011-01-04 13:44 ` Peter Zijlstra
2011-01-04 13:52 ` Stephane Eranian
2011-01-04 13:58 ` Peter Zijlstra
2011-01-04 15:35 ` Stephane Eranian
2011-01-04 19:00 ` H. Peter Anvin
2011-01-05 5:45 ` Lin Ming
2011-01-05 10:08 ` Peter Zijlstra
2011-01-04 18:55 ` Valdis.Kletnieks [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=14831.1294167327@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.