From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: eranian@google.com, mingo@elte.hu, andi@firstfloor.org,
jolsa@redhat.com, linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [RFC PATCH 1/3] perf: Add cpumask for uncore pmu
Date: Mon, 10 Sep 2012 18:34:26 +0200 [thread overview]
Message-ID: <1347294866.2124.28.camel@twins> (raw)
In-Reply-To: <1347263631-23175-1-git-send-email-zheng.z.yan@intel.com>
On Mon, 2012-09-10 at 15:53 +0800, Yan, Zheng wrote:
> Hi,
>
> This patchset add a cpumask file to the uncore pmu sysfs directory.
> If user doesn't explicitly specify CPU list, perf-stat only collects
> uncore events on CPUs listed in the cpumask file.
>
> As Stephane suggested, make perf-stat recognize wildcard in pmu name.
> So we can easily measure event on all uncore boxes of same type.
>
> Any comment is appreciated.
You forgot to CC acme who maintains the tools side.. Anyway, I think it
all looks ok, Arnaldo see anything dubious in there?
next prev parent reply other threads:[~2012-09-10 16:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 7:53 [RFC PATCH 1/3] perf: Add cpumask for uncore pmu Yan, Zheng
2012-09-10 7:53 ` [RFC PATCH 1/3] perf/x86: " Yan, Zheng
2012-09-19 15:26 ` [tip:perf/core] " tip-bot for Yan, Zheng
2012-09-10 7:53 ` [RFC PATCH 2/3] perf tool: Make perf-stat check PMU cpumask file Yan, Zheng
2012-09-19 15:26 ` [tip:perf/core] perf stat: Check " tip-bot for Yan, Zheng
2012-09-10 7:53 ` [RFC PATCH 3/3] perf tool: Allow wildcard in PMU name Yan, Zheng
2012-09-11 13:50 ` Jiri Olsa
2012-09-11 14:05 ` Jiri Olsa
2012-09-12 1:30 ` Yan, Zheng
2012-09-12 9:03 ` Jiri Olsa
2012-09-11 14:27 ` Jiri Olsa
2012-09-17 15:36 ` Arnaldo Carvalho de Melo
2012-09-18 3:11 ` Yan, Zheng
2012-09-10 16:34 ` Peter Zijlstra [this message]
2012-09-10 23:10 ` [RFC PATCH 1/3] perf: Add cpumask for uncore pmu Arnaldo Carvalho de Melo
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=1347294866.2124.28.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zheng.z.yan@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 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.