From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 4/4] perf: Avoid the percore allocations if HT is not capable
Date: Thu, 3 Mar 2011 10:34:50 +0800 [thread overview]
Message-ID: <1299119690-13991-5-git-send-email-ming.m.lin@intel.com> (raw)
In-Reply-To: <1299119690-13991-4-git-send-email-ming.m.lin@intel.com>
No need to do percore allocations if HT is not capable
Signed-off-by: Lin Ming <ming.m.lin@intel.com>
---
arch/x86/kernel/cpu/perf_event_intel.c | 23 +++++++++++++++++------
1 files changed, 17 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kernel/cpu/perf_event_intel.c b/arch/x86/kernel/cpu/perf_event_intel.c
index aaac4a9..4bee70a 100644
--- a/arch/x86/kernel/cpu/perf_event_intel.c
+++ b/arch/x86/kernel/cpu/perf_event_intel.c
@@ -1201,10 +1201,18 @@ static __initconst const struct x86_pmu core_pmu = {
.event_constraints = intel_core_event_constraints,
};
+static bool ht_capable(void)
+{
+ return boot_cpu_has(X86_FEATURE_HT) && smp_num_siblings > 1;
+}
+
static int intel_pmu_cpu_prepare(int cpu)
{
struct cpu_hw_events *cpuc = &per_cpu(cpu_hw_events, cpu);
+ if (!ht_capable())
+ return NOTIFY_OK;
+
cpuc->per_core = kzalloc_node(sizeof(struct intel_percore),
GFP_KERNEL, cpu_to_node(cpu));
if (!cpuc->per_core)
@@ -1221,6 +1229,15 @@ static void intel_pmu_cpu_starting(int cpu)
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_capable())
+ return;
+
for_each_cpu(i, topology_thread_cpumask(cpu)) {
struct intel_percore *pc = per_cpu(cpu_hw_events, i).per_core;
@@ -1233,12 +1250,6 @@ static void intel_pmu_cpu_starting(int cpu)
cpuc->per_core->core_id = core_id;
cpuc->per_core->refcnt++;
-
- init_debug_store_on_cpu(cpu);
- /*
- * Deal with CPUs that don't clear their LBRs on power-up.
- */
- intel_pmu_lbr_reset();
}
static void intel_pmu_cpu_dying(int cpu)
--
1.7.3
next prev parent reply other threads:[~2011-03-03 2:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 2:34 [PATCH v3 0/4] perf: offcore event monitoring patches Lin Ming
2011-03-03 2:34 ` [PATCH v3 1/4] perf: Add support for supplementary event registers Lin Ming
2011-03-03 2:34 ` [PATCH v3 2/4] perf: Fix LLC-* events on Intel Nehalem/Westmere Lin Ming
2011-03-03 2:34 ` [PATCH v3 3/4] perf: Add support to the perf tool to specify extra values Lin Ming
2011-03-03 2:34 ` Lin Ming [this message]
2011-03-04 13:04 ` [tip:perf/core] perf: Avoid the percore allocations if the CPU is not HT capable tip-bot for Lin Ming
2011-03-05 15:52 ` tip-bot for Lin Ming
2011-03-04 11:53 ` [tip:perf/core] perf: Fix LLC-* events on Intel Nehalem/Westmere tip-bot for Andi Kleen
2011-05-06 9:43 ` [tip:perf/urgent] perf events, x86: Fix Intel Nehalem and Westmere last level cache event definitions tip-bot for Peter Zijlstra
2011-03-04 11:53 ` [tip:perf/core] perf: Add support for supplementary event registers tip-bot for Andi Kleen
2011-03-03 10:14 ` [PATCH v3 0/4] perf: offcore event monitoring patches Peter Zijlstra
2011-03-04 1:16 ` Lin Ming
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=1299119690-13991-5-git-send-email-ming.m.lin@intel.com \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®