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, tglx@linutronix.de,
andi@firstfloor.org, drepper@gmail.com
Subject: [PATCHv3 0/3] perf tool: Add new event group management
Date: Fri, 29 Jun 2012 11:08:24 +0200 [thread overview]
Message-ID: <1340960907-3725-1-git-send-email-jolsa@redhat.com> (raw)
hi,
adding support for creating event groups based on the way they
are specified on the command line.
This patchset adds the '{}' style grammar to express event group,
allowing so far only the 'event modifier' as group modifier.
The sample/leader modifier changes are ready, but I'm getting
some weird numbers in tests, so I'll send it later. Meanwhile,
it'd be nice to have at least this patchset in.. ;)
Attached patches:
1/3 perf, tool: Add support to parse event group syntax
2/3 perf, tool: Enable grouping logic for parsed events
3/3 perf, test: Add automated tests for event group parsing
wbr,
jirka
---
tools/perf/builtin-record.c | 13 +--
tools/perf/builtin-stat.c | 13 +--
tools/perf/builtin-test.c | 8 +-
tools/perf/builtin-top.c | 12 +--
tools/perf/util/evlist.c | 20 ++---
tools/perf/util/evlist.h | 3 +-
tools/perf/util/evsel.c | 51 ++++++++----
tools/perf/util/evsel.h | 11 +--
tools/perf/util/parse-events-test.c | 152 +++++++++++++++++++++++++++++++++++
tools/perf/util/parse-events.c | 32 +++++++-
tools/perf/util/parse-events.h | 5 +-
tools/perf/util/parse-events.l | 2 +
tools/perf/util/parse-events.y | 93 ++++++++++++++++++---
tools/perf/util/python.c | 7 +-
14 files changed, 341 insertions(+), 81 deletions(-)
next reply other threads:[~2012-06-29 9:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 9:08 Jiri Olsa [this message]
2012-06-29 9:08 ` [PATCH 1/3] perf, tool: Add support to parse event group syntax Jiri Olsa
2012-06-29 9:08 ` [PATCH 2/3] perf, tool: Enable grouping logic for parsed events Jiri Olsa
2012-06-29 16:47 ` Arnaldo Carvalho de Melo
2012-06-29 16:53 ` Jiri Olsa
2012-07-02 2:13 ` Namhyung Kim
2012-07-02 10:10 ` Jiri Olsa
2012-07-03 0:58 ` Namhyung Kim
2012-07-04 17:34 ` Jiri Olsa
2012-07-05 0:45 ` Namhyung Kim
2012-07-05 16:05 ` Peter Zijlstra
2012-07-05 16:43 ` Arnaldo Carvalho de Melo
2012-06-29 9:08 ` [PATCH 3/3] perf, test: Add automated tests for event group parsing Jiri Olsa
2012-07-02 1:53 ` [PATCHv3 0/3] perf tool: Add new event group management Namhyung Kim
2012-07-02 10:15 ` Jiri Olsa
2012-07-02 13:11 ` Namhyung Kim
2012-07-02 13:33 ` Jiri Olsa
2012-07-02 14:20 ` Namhyung Kim
2012-07-03 0:50 ` Namhyung Kim
2012-07-03 1:04 ` Arnaldo Carvalho de Melo
2012-07-05 16:15 ` Stephane Eranian
2012-07-05 16:44 ` Arnaldo Carvalho de Melo
2012-07-06 1:06 ` Stephane Eranian
2012-07-06 1:32 ` Ulrich Drepper
2012-07-06 1:42 ` Stephane Eranian
2012-07-09 11:05 ` Jiri Olsa
2012-07-09 11:15 ` Peter Zijlstra
2012-07-17 7:15 ` Stephane Eranian
2012-07-17 15:47 ` Andi Kleen
2012-07-18 10:21 ` Jiri Olsa
2012-07-18 12:34 ` Ulrich Drepper
2012-07-18 20:06 ` Jiri Olsa
2012-07-05 16:09 ` Stephane Eranian
2012-07-02 2:25 ` David Ahern
2012-07-02 10:07 ` Jiri Olsa
2012-07-02 10:19 ` Peter Zijlstra
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=1340960907-3725-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=drepper@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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).