mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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/8] perf tool: event parsing enhancements/fixes
Date: Wed,  4 Apr 2012 22:21:30 +0200	[thread overview]
Message-ID: <1333570898-10505-1-git-send-email-jolsa@redhat.com> (raw)

Hi,
adding some enhancements/fixies for perf event parsing.

- patch 1 is simple fix

- patches 2, 3, 4 and 5 are event config terms enhancements

- patches 6, 7 and 8 are maintanance patches either helping
  with developement (6, 7) or making the code more clear (8).

Attached patches:
 1/8 perf, tool: Fix NULL deref in hists browsing code
 2/8 perf, tool: Split term type into value type and term type
 3/8 perf, tool: Add list type for event term parsing
 4/8 perf, tool: Add hardcoded name term for pmu events
 5/8 perf, tool: Add pmu event parse support for branch_sample_type values
 6/8 perf, tool: Move parse event automated tests to separated object
 7/8 perf, tool: Add support for displaying event parser debug info
 8/8 perf, tool: Use allocated list for each parsed event

thanks,
jirka
---
 tools/perf/Makefile                 |   13 +-
 tools/perf/builtin-record.c         |   31 +--
 tools/perf/builtin-test.c           |  522 +-------------------------------
 tools/perf/util/parse-events-test.c |  588 +++++++++++++++++++++++++++++++++++
 tools/perf/util/parse-events.c      |  240 +++++++++++++--
 tools/perf/util/parse-events.h      |   59 +++-
 tools/perf/util/parse-events.l      |    2 +
 tools/perf/util/parse-events.y      |  147 ++++++++--
 tools/perf/util/pmu.c               |   85 ++++--
 tools/perf/util/pmu.h               |    2 +
 tools/perf/util/ui/browsers/hists.c |    3 +
 11 files changed, 1037 insertions(+), 655 deletions(-)

             reply	other threads:[~2012-04-04 20:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 20:21 Jiri Olsa [this message]
2012-04-04 20:21 ` [PATCH 1/8] perf, tool: Fix NULL deref in hists browsing code Jiri Olsa
2012-04-13 18:04   ` [tip:perf/core] perf hists browser: " tip-bot for Jiri Olsa
2012-04-04 20:21 ` [PATCH 2/8] perf, tool: Split term type into value type and term type Jiri Olsa
2012-04-04 20:21 ` [PATCH 3/8] perf, tool: Add list type for event term parsing Jiri Olsa
2012-04-04 20:21 ` [PATCH 4/8] perf, tool: Add hardcoded name term for pmu events Jiri Olsa
2012-04-04 20:21 ` [PATCH 5/8] perf, tool: Add pmu event parse support for branch_sample_type values Jiri Olsa
2012-04-05  4:50   ` Stephane Eranian
2012-04-05  8:59     ` Jiri Olsa
2012-04-05 17:06       ` Stephane Eranian
2012-04-04 20:21 ` [PATCH 6/8] perf, tool: Move parse event automated tests to separated object Jiri Olsa
2012-04-04 20:21 ` [PATCH 7/8] perf, tool: Add support for displaying event parser debug info Jiri Olsa
2012-04-04 20:21 ` [PATCH 8/8] perf, tool: Use allocated list for each parsed event 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=1333570898-10505-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

all inboxes | Powered by JetHome®