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: [RFC 0/3] perf tool: Add new event group management
Date: Tue, 20 Mar 2012 19:15:38 +0100 [thread overview]
Message-ID: <1332267341-26338-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. Also attaching several fixies
to current code.
attached patches:
1/3 perf, tool: Fix various casting issues for 32 bits
2/3 perf, tool: Fix modifier to be applied on correct events
3/3 perf, tool: Add new event group management
I added automated tests and run some record and stats tests
based on the examples (attached in the 3/3 changelog), and
so far so good..
thanks for comments,
jirka
---
tools/perf/Makefile | 2 +
tools/perf/builtin-record.c | 8 +-
tools/perf/builtin-stat.c | 10 +-
tools/perf/builtin-test.c | 126 +++++++-
tools/perf/builtin-top.c | 8 +-
tools/perf/perf.h | 3 +-
tools/perf/util/evlist.c | 4 +-
tools/perf/util/evlist.h | 3 +-
tools/perf/util/evsel.c | 32 ++-
tools/perf/util/evsel.h | 9 +-
tools/perf/util/group.c | 22 ++
tools/perf/util/group.h | 32 ++
tools/perf/util/header.c | 2 +-
tools/perf/util/parse-events-bison.c | 675 +++++++++++++++++++---------------
tools/perf/util/parse-events-bison.h | 15 +-
tools/perf/util/parse-events.c | 47 ++-
tools/perf/util/parse-events.h | 10 +-
tools/perf/util/parse-events.y | 40 ++-
tools/perf/util/python.c | 4 +
tools/perf/util/top.h | 2 +-
20 files changed, 687 insertions(+), 367 deletions(-)
next reply other threads:[~2012-03-20 18:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 18:15 Jiri Olsa [this message]
2012-03-20 18:15 ` [PATCH 1/3] perf, tool: Fix various casting issues for 32 bits Jiri Olsa
2012-03-23 8:29 ` [tip:perf/urgent] perf tools: " tip-bot for Jiri Olsa
2012-03-20 18:15 ` [PATCH 2/3] perf, tool: Fix modifier to be applied on correct events Jiri Olsa
2012-03-23 8:30 ` [tip:perf/urgent] perf tools: " tip-bot for Jiri Olsa
2012-03-20 18:15 ` [PATCH 3/3] perf, tool: Add new event group management Jiri Olsa
2012-03-20 18:44 ` Peter Zijlstra
2012-03-20 20:46 ` Ingo Molnar
2012-03-20 22:18 ` Arnaldo Carvalho de Melo
2012-03-21 9:15 ` Peter Zijlstra
2012-03-21 9:52 ` Ingo Molnar
2012-03-21 11:54 ` Peter Zijlstra
2012-03-21 12:15 ` Ingo Molnar
2012-03-21 15:13 ` Arnaldo Carvalho de Melo
2012-03-22 7:56 ` Ingo Molnar
2012-03-22 12:41 ` Arnaldo Carvalho de Melo
2012-03-22 13:54 ` Ingo Molnar
2012-03-22 14:07 ` Jiri Olsa
2012-03-20 22:36 ` Jiri Olsa
2012-03-21 11:54 ` Peter Zijlstra
2012-03-21 10:42 ` Jiri Olsa
2012-03-21 15:11 ` Arnaldo Carvalho de Melo
2012-03-21 22:27 ` Jiri Olsa
2012-03-22 12:40 ` Arnaldo Carvalho de Melo
2012-04-10 13:19 ` Jiri Olsa
2012-03-20 20:08 ` Arnaldo Carvalho de Melo
2012-03-20 22:16 ` Jiri Olsa
2012-03-21 2:12 ` Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2011-12-15 15:30 [RFC 0/3] perf " 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=1332267341-26338-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;
as well as URLs for NNTP newsgroup(s).