From: Lin Ming <ming.m.lin@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] perf, x86: Add Intel Nehalem/Westmere uncore pmu
Date: Mon, 04 Jul 2011 14:39:01 +0800 [thread overview]
Message-ID: <1309761541.18875.40.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <20110630165849.GE23059@one.firstfloor.org>
On Fri, 2011-07-01 at 00:58 +0800, Andi Kleen wrote:
> On Thu, Jun 30, 2011 at 08:09:53AM +0000, Lin Ming wrote:
> > +static u64 uncore_perf_event_update(struct perf_event *event)
> > +{
> > + struct hw_perf_event *hwc = &event->hw;
> > + int shift = 64 - intel_uncore_pmu.cntval_bits;
> > + u64 prev_raw_count, new_raw_count;
> > + s64 delta;
> > +
> > + /*
> > + * Careful: an NMI might modify the previous event value.
>
> There are no NMIs without sampling, so at least the comment seems bogus.
> Perhaps the code could be a bit simplified now without atomics.
I'm not sure if uncore PMU interrupt need to be enabled for counting
only. What do you think?
>
> > +static int uncore_pmu_event_init(struct perf_event *event)
> > +{
> > + struct hw_perf_event *hwc = &event->hw;
> > +
> > + if (!uncore_pmu_initialized)
> > + return -ENOENT;
> > +
> > + if (event->attr.type != uncore_pmu.type)
> > + return -ENOENT;
> > +
> > + /*
> > + * Uncore PMU does measure at all privilege level all the time.
> > + * So it doesn't make sense to specify any exclude bits.
> > + */
> > + if (event->attr.exclude_user || event->attr.exclude_kernel
> > + || event->attr.exclude_hv || event->attr.exclude_idle)
> > + return -ENOENT;
> > +
> > + /* Sampling not supported yet */
> > + if (hwc->sample_period)
> > + return -EINVAL;
>
> Don't we need a "is root" check here? uncore counts everything, so
> it cannot be limited to a single process.
Yes, will add a "is root" check.
Will add .task_ctx_nr = perf_invalid_context to disallow per-process
counting.
>
> > +static void uncore_pmu_cpu_starting(int cpu)
> > +{
> > + struct cpu_uncore_events *cpuc = &per_cpu(cpu_uncore_events, cpu);
> > + struct intel_uncore *uncore;
> > + int i, uncore_id;
> > +
> > + if (boot_cpu_data.x86_max_cores < 2)
> > + return;
>
> Why that check? uncore counting should work on a single core system too.
>
> I think you should remove all of those.
Agree, will remove it.
>
> > +
> > + uncore_id = topology_physical_package_id(cpu);
> > + WARN_ON_ONCE(uncore_id == BAD_APICID);
> > +
> > + raw_spin_lock(&intel_uncore_lock);
>
> Does this really need to be a raw spinlock?
I think spinlock is enough.
>
> > +#define NHM_MSR_UNCORE_PERF_GLOBAL_CTRL 0x391
> > +#define NHM_MSR_UNCORE_PMC0 0x3b0
> > +#define NHM_MSR_UNCORE_PERFEVTSEL0 0x3c0
>
> These should be in msr-index.h
Will move these.
Thanks,
Lin Ming
>
>
> -Andi
next prev parent reply other threads:[~2011-07-04 6:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 8:09 [PATCH 0/4] perf: Intel uncore pmu counting support Lin Ming
2011-06-30 8:09 ` [PATCH 1/4] perf, x86: Add Intel Nehalem/Westmere uncore pmu Lin Ming
2011-06-30 14:08 ` Peter Zijlstra
2011-07-01 6:05 ` Lin Ming
2011-06-30 16:58 ` Andi Kleen
2011-07-04 6:39 ` Lin Ming [this message]
2011-07-04 8:38 ` Peter Zijlstra
2011-07-04 21:57 ` Andi Kleen
2011-07-05 11:22 ` Peter Zijlstra
2011-07-05 12:48 ` Lin Ming
2011-07-05 12:56 ` Peter Zijlstra
2011-07-05 13:13 ` Lin Ming
2011-07-05 16:01 ` Andi Kleen
2011-07-06 9:35 ` Ingo Molnar
2011-06-30 8:09 ` [PATCH 2/4] perf, x86: Add Intel SandyBridge " Lin Ming
2011-06-30 22:09 ` Peter Zijlstra
2011-06-30 8:09 ` [PATCH 3/4] perf: Remove perf_event_attr::type check Lin Ming
2011-07-21 19:31 ` [tip:perf/core] " tip-bot for Lin Ming
2011-06-30 8:09 ` [PATCH 4/4] perf tool: Get PMU type id from sysfs Lin Ming
2011-06-30 12:10 ` [PATCH 0/4] perf: Intel uncore pmu counting support Stephane Eranian
2011-06-30 14:10 ` Peter Zijlstra
2011-06-30 16:27 ` Stephane Eranian
2011-07-01 3:17 ` Lin Ming
2011-07-01 10:49 ` Stephane Eranian
2011-07-01 12:23 ` Stephane Eranian
2011-07-01 12:28 ` Stephane Eranian
2011-07-04 6:03 ` Lin Ming
2011-07-01 5:49 ` Lin Ming
2011-07-01 11:08 ` Ingo Molnar
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=1309761541.18875.40.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--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