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
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH/RFC 0/5] perf tool: event parsing enhancements
Date: Wed, 28 Mar 2012 17:55:48 +0200 [thread overview]
Message-ID: <1332950153-8606-1-git-send-email-jolsa@redhat.com> (raw)
hi,
sending some enhancements for event parsing.
There are basically 2 features:
- adding hardcoded term 'name' to allow specifying a name
for the pmu event (patch 1/5)
- implement hardcoded term 'branch_type' and allow specifying
values like "branch_type=hv|any_ret|1" (patches 2-4/5)
Also, I was thinking of some overall event syntax documentation,
so I outlined something in patch 5/5. It's unfinished, highly
mistyped and partly stolen stuff.
What I'd expect would be some feedback about the form. Like what
it should look like.. event syntax + description of each event
type, modifiers etc.. please be gentle, it's RFC ;)
Attached patches:
1/5 perf, tool: Add hardcoded name term for pmu events
2/5 perf, tool: Split term type into value type and term type
3/5 perf, tool: Add list type for event term parsing
4/5 perf, tool: Add pmu event parse support for branch_sample_type values
5/5 perf, tool: Add events specification doc
thanks,
jirka
---
tools/perf/Documentation/perf-events.txt | 182 +++++++
tools/perf/Documentation/perf-record.txt | 2 +-
tools/perf/Documentation/perf-stat.txt | 2 +-
tools/perf/builtin-record.c | 31 +-
tools/perf/builtin-test.c | 53 ++
tools/perf/util/parse-events-bison.c | 799 ++++++++++++++++--------------
tools/perf/util/parse-events-bison.h | 16 +-
tools/perf/util/parse-events-flex.c | 597 ++++++++++++-----------
tools/perf/util/parse-events-flex.h | 2 +-
tools/perf/util/parse-events.c | 194 +++++++-
tools/perf/util/parse-events.h | 40 ++-
tools/perf/util/parse-events.l | 2 +
tools/perf/util/parse-events.y | 79 +++-
tools/perf/util/pmu.c | 85 ++--
tools/perf/util/pmu.h | 2 +
15 files changed, 1321 insertions(+), 765 deletions(-)
next reply other threads:[~2012-03-28 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 15:55 Jiri Olsa [this message]
2012-03-28 15:55 ` [PATCH 1/5] perf, tool: Add hardcoded name term for pmu events Jiri Olsa
2012-03-28 15:55 ` [PATCH 2/5] perf, tool: Split term type into value type and term type Jiri Olsa
2012-03-28 15:55 ` [PATCH 3/5] perf, tool: Add list type for event term parsing Jiri Olsa
2012-03-28 15:55 ` [PATCH 4/5] perf, tool: Add pmu event parse support for branch_sample_type values Jiri Olsa
2012-03-28 15:55 ` [RFC 5/5] perf, tool: Add events specification doc Jiri Olsa
2012-03-29 1:35 ` Namhyung Kim
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=1332950153-8606-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.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
Powered by JetHome