From: Jiri Olsa <jolsa@redhat.com>
To: acme@redhat.com, a.p.zijlstra@chello.nl, mingo@elte.hu,
paulus@samba.org, cjashfor@linux.vnet.ibm.com,
fweisbec@gmail.com, eranian@google.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 0/6] perf, tool: Allow to use hw events in PMU syntax
Date: Wed, 8 Aug 2012 14:42:14 +0200 [thread overview]
Message-ID: <20120808124214.GC959@krava.brq.redhat.com> (raw)
In-Reply-To: <1341866270-4915-1-git-send-email-jolsa@redhat.com>
On Mon, Jul 09, 2012 at 10:37:44PM +0200, Jiri Olsa wrote:
> hi,
> here's the change to make following syntax available:
> perf stat -e cpu/event=instructions/u ls
>
> this is identical to:
> perf stat -e instructions:u ls
>
> v3 changes:
> - patches v2 1,5,6,9 are already in
> - patch 1 - sysfs 'events' attribute file names with dashes '-'
> - using 'event/umask/inv/cmask' terms assigments instead simple 'config'
> - patch 2 - undefined events sysfs attributes filtered out
>
> v2 changes:
> - making the hw events translations available under the 'events',
> the userspace trnaslation is then done by existing term aliasing
> code with some little tweeks ;)
> - patches 1-3 are independent fixies
>
> Attached patches:
> 1/6 perf, x86: Making hardware events translations available in sysfs
> 2/6 perf, x86: Filter out undefined events from sysfs events attribute
> 3/6 perf, tool: Fix pmu object alias initialization
> 4/6 perf, tool: Properly free format data
> 5/6 perf, tool: Add support to specify hw event as pmu event term
> 6/6 perf, test: Add automated tests for pmu sysfs translated events
>
> jirka
> ---
> arch/x86/kernel/cpu/perf_event.c | 98 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> tools/perf/util/parse-events-test.c | 75 +++++++++++++++++++++++++++++++++++++++++++++++--
> tools/perf/util/parse-events.c | 13 +++++++++
> tools/perf/util/parse-events.h | 2 ++
> tools/perf/util/parse-events.y | 9 ++++++
> tools/perf/util/pmu.c | 59 ++++++++++++++++++++++++---------------
> 6 files changed, 232 insertions(+), 24 deletions(-)
hi,
any feedback on this?
you can check rebased version (on Arnaldo's perf/core) here:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/linux.git
perf/sysfs_events1
thanks,
jirka
next prev parent reply other threads:[~2012-08-08 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 20:37 [PATCHv3 0/6] perf, tool: Allow to use hw events in PMU syntax Jiri Olsa
2012-07-09 20:37 ` [PATCH 1/6] perf, x86: Making hardware events translations available in sysfs Jiri Olsa
2012-08-20 8:25 ` Stephane Eranian
2012-08-20 9:55 ` Jiri Olsa
2012-07-09 20:37 ` [PATCH 2/6] perf, x86: Filter out undefined events from sysfs events attribute Jiri Olsa
2012-07-09 20:37 ` [PATCH 3/6] perf, tool: Fix pmu object alias initialization Jiri Olsa
2012-07-09 20:37 ` [PATCH 4/6] perf, tool: Properly free format data Jiri Olsa
2012-07-09 20:37 ` [PATCH 5/6] perf, tool: Add support to specify hw event as pmu event term Jiri Olsa
2012-07-09 20:37 ` [PATCH 6/6] perf, test: Add automated tests for pmu sysfs translated events Jiri Olsa
2012-08-08 12:42 ` Jiri Olsa [this message]
2012-08-16 13:44 ` [PATCHv3 0/6] perf, tool: Allow to use hw events in PMU syntax Jiri Olsa
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=20120808124214.GC959@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).