From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Stephane Eranian <eranian@google.com>,
"Luck, Tony" <tony.luck@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <andi@firstfloor.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/7] perf: Check if HT is supported and enabled
Date: Wed, 05 Jan 2011 11:08:41 +0100 [thread overview]
Message-ID: <1294222121.2016.221.camel@laptop> (raw)
In-Reply-To: <1294206320.9261.23.camel@minggr.sh.intel.com>
On Wed, 2011-01-05 at 13:45 +0800, Lin Ming wrote:
> static void intel_pmu_cpu_starting(int cpu)
> {
> struct cpu_hw_events *cpuc = &per_cpu(cpu_hw_events, cpu);
> struct intel_percore *pc;
> int core_id = topology_core_id(cpu);
> int i;
>
> init_debug_store_on_cpu(cpu);
> /*
> * Deal with CPUs that don't clear their LBRs on power-up.
> */
> intel_pmu_lbr_reset();
>
> if (!ht_enabled(cpu))
> return;
>
> cpuc->per_core = kzalloc_node(sizeof(struct intel_percore),
> GFP_KERNEL, cpu_to_node(cpu));
#define CPU_STARTING 0x000A /* CPU (unsigned)v soon running.
* Called on the new cpu, just before
* enabling interrupts. Must not sleep,
* must not fail */
> if (!cpuc->per_core)
> return;
>
> raw_spin_lock_init(&cpuc->per_core->lock);
> pc = cpuc->per_core;
>
> for_each_cpu(i, topology_thread_cpumask(cpu)) {
> cpuc = &per_cpu(cpu_hw_events, cpu);
>
> cpuc->per_core = pc;
> cpuc->per_core->core_id = core_id;
> cpuc->per_core->refcnt++;
> }
> }
Anyway, I think something like:
static bool ht_capable(void)
{
return boot_cpu_has(X86_FEATURE_HT) && smp_num_siblings > 1;
}
is sufficient, the whole hotplug issues makes relying on enumeration
results impractical.
next prev parent reply other threads:[~2011-01-05 10:08 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 [this message]
2011-01-04 18:55 ` Valdis.Kletnieks
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=1294222121.2016.221.camel@laptop \
--to=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 \
--cc=tony.luck@intel.com \
/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