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 0/6] perf, tool: event parsing enhancements/fixes
Date: Sun, 15 Apr 2012 15:40:28 +0200 [thread overview]
Message-ID: <1334497234-5441-1-git-send-email-jolsa@redhat.com> (raw)
Hi,
adding some enhancements/fixies for perf event parsing.
Attached patches:
1/6 perf, tool: Split term type into value type and term type
2/6 perf, tool: Move parse event automated tests to separated object
3/6 perf, tool: Add support for displaying event parser debug info
4/6 perf, tool: Use allocated list for each parsed event
5/6 perf, tool: Separate 'mem:' event scanner bits
6/6 perf, tool: Add hardcoded name term for pmu events
thanks,
jirka
---
tools/perf/Makefile | 13 +-
tools/perf/builtin-test.c | 522 +--------------------------------
tools/perf/util/parse-events-test.c | 560 +++++++++++++++++++++++++++++++++++
tools/perf/util/parse-events.c | 103 +++++--
tools/perf/util/parse-events.h | 43 ++--
tools/perf/util/parse-events.l | 26 ++-
tools/perf/util/parse-events.y | 93 +++++--
tools/perf/util/pmu.c | 85 ++++--
tools/perf/util/pmu.h | 2 +
9 files changed, 821 insertions(+), 626 deletions(-)
next reply other threads:[~2012-04-15 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 13:40 Jiri Olsa [this message]
2012-04-15 13:40 ` [PATCH 1/6] perf, tool: Split term type into value type and term type Jiri Olsa
2012-04-15 13:40 ` [PATCH 2/6] perf, tool: Move parse event automated tests to separated object Jiri Olsa
2012-04-15 13:40 ` [PATCH 3/6] perf, tool: Add support for displaying event parser debug info Jiri Olsa
2012-04-15 13:40 ` [PATCH 4/6] perf, tool: Use allocated list for each parsed event Jiri Olsa
2012-04-15 13:40 ` [PATCH 5/6] perf, tool: Separate 'mem:' event scanner bits Jiri Olsa
2012-04-15 13:40 ` [PATCH 6/6] perf, tool: Add hardcoded name term for pmu events 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=1334497234-5441-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