public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: acme@redhat.com, a.p.zijlstra@chello.nl, mingo@elte.hu,
	paulus@samba.org, cjashfor@linux.vnet.ibm.com,
	fweisbec@gmail.com, linux-kernel@vger.kernel.org,
	eranian@google.com, robert.richter@amd.com
Subject: Re: [PATCHv2 0/6] perf, tool: event parsing enhancements/fixes
Date: Thu, 26 Apr 2012 12:10:30 +0200	[thread overview]
Message-ID: <20120426101030.GA1659@m.brq.redhat.com> (raw)
In-Reply-To: <87liljf2gi.fsf@sejong.aot.lge.com>

On Thu, Apr 26, 2012 at 03:10:21PM +0900, Namhyung Kim wrote:
> Hi,
> 
> On Wed, 25 Apr 2012 18:24:56 +0200, Jiri Olsa wrote:
> > Hi,
> > adding some enhancements/fixies for perf event parsing.
> >
> > v2 changes:
> >    - rebased to current tip tree
> >    - 2/6 - ommitting pmu tests in case there's no pmu sysfs record
> 
> Nice! It bothered me somewhat so I was thinking about fixing it.
> I guess we have a same problem on x86 rdpmc test too?

right.. I haven't seen that code, so not sure how hard the fix would be

jirka

> 
> Thanks,
> Namhyung
> 
> 
> >    - 6/6 - default the pmu event name to raw 0x<perf_event_attr::config>
> >
> > 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           |  552 +------------------------------
> >  tools/perf/util/parse-events-test.c |  625 +++++++++++++++++++++++++++++++++++
> >  tools/perf/util/parse-events.c      |  114 +++++--
> >  tools/perf/util/parse-events.h      |   42 ++-
> >  tools/perf/util/parse-events.l      |   26 ++-
> >  tools/perf/util/parse-events.y      |   93 ++++--
> >  tools/perf/util/pmu.c               |   74 +++--
> >  8 files changed, 883 insertions(+), 656 deletions(-)

      reply	other threads:[~2012-04-26 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 16:24 [PATCHv2 0/6] perf, tool: event parsing enhancements/fixes Jiri Olsa
2012-04-25 16:24 ` [PATCH 1/6] perf, tool: Split term type into value type and term type Jiri Olsa
2012-05-21  7:40   ` [tip:perf/core] perf tools: " tip-bot for Jiri Olsa
2012-04-25 16:24 ` [PATCH 2/6] perf, tool: Move parse event automated tests to separated object Jiri Olsa
2012-04-25 16:24 ` [PATCH 3/6] perf, tool: Add support for displaying event parser debug info Jiri Olsa
2012-04-25 16:25 ` [PATCH 4/6] perf, tool: Use allocated list for each parsed event Jiri Olsa
2012-04-25 16:25 ` [PATCH 5/6] perf, tool: Separate 'mem:' event scanner bits Jiri Olsa
2012-04-25 16:25 ` [PATCH 6/6] perf, tool: Add hardcoded name term for pmu events Jiri Olsa
2012-04-26  6:10 ` [PATCHv2 0/6] perf, tool: event parsing enhancements/fixes Namhyung Kim
2012-04-26 10:10   ` Jiri Olsa [this message]

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=20120426101030.GA1659@m.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung.kim@lge.com \
    --cc=paulus@samba.org \
    --cc=robert.richter@amd.com \
    /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