public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Jiri Olsa <jolsa@redhat.com>,
	mingo@elte.hu, paulus@samba.org, cjashfor@linux.vnet.ibm.com,
	fweisbec@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5 0/8] perf tool: parser generator for events parsing
Date: Thu, 16 Feb 2012 15:35:34 -0200	[thread overview]
Message-ID: <20120216173534.GG27941@infradead.org> (raw)
In-Reply-To: <1329411783.2293.257.camel@twins>

Em Thu, Feb 16, 2012 at 06:03:03PM +0100, Peter Zijlstra escreveu:
> On Thu, 2012-02-16 at 13:00 +0100, Jiri Olsa wrote:
> > hi,
> > here's new version of event parsing patchset.
> > 
> > I saw Arnaldo already sent patches 1-3 to Ingo, but they did not make it
> > to the tree yet, so I'm still attaching them here.

Right, I'll take the rest (read this just now, keeping the dup comments
below :-) ).

> > v5 changes:
> >  4/8 - patch updated by Peter with actual format definitions
> >        for x86 processors
> >  6/8 - added hardcoded terms for config[12] and sample_period
> >        the code is ready to include branch_sample_type once
> >        this field is available in perf_event_attr, just
> >        uncommenting one line.. ;) 
> >      - allow config option to be used without value in which
> >        case 1 is assigned as value
> > 
> > Overall summarize:
> >  - adding event parser bison/flex generator
> >  - the event syntax stays as it was
> >  - adding event format sysfs group attribute
> >    for pmu device
> >  - adding new syntax to specify raw events based
> >    on the sysfs pmu's format attribute
> >    eg. "cpu/config=1,config1=2,config2=3/u"
> > 
> > Attached patches:
> >  1/8 perf, tool: Remove unused functions from debugfs object
> >  2/8 perf, tool: Add sysfs mountpoint interface
> >  3/8 perf, tool: Add bitmap_or function into bitmap object
> >  4/8 perf: Adding sysfs group format attribute for pmu device
> >  5/8 perf, tool: Add parser generator for events parsing
> >  6/8 perf, tool: Add config options support for event parsing
> >  7/8 perf, tool: Add perf pmu object to access pmu format definition
> >  8/8 perf, tool: Add support to specify pmu style event
> 
> I'm fine with this going fwd, and since this is mostly tools/perf I
> suggest acme take it, so:
> 
> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> 
> Also, it might make sense to CC everybody who has/maintains a hardware
> pmu implementation on patch 4.

I'll do it, I already merged patch 1, 2, 3 in my perf/core branch, will
look and merge the rest, adding your a-b.

- Arnaldo

      reply	other threads:[~2012-02-16 18:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 12:00 [PATCHv5 0/8] perf tool: parser generator for events parsing Jiri Olsa
2012-02-16 12:00 ` [PATCH 1/8] perf, tool: Remove unused functions from debugfs object Jiri Olsa
2012-02-16 12:00 ` [PATCH 2/8] perf, tool: Add sysfs mountpoint interface Jiri Olsa
2012-02-16 12:00 ` [PATCH 3/8] perf, tool: Add bitmap_or function into bitmap object Jiri Olsa
2012-02-16 12:00 ` [PATCH 4/8] perf: Adding sysfs group format attribute for pmu device Jiri Olsa
2012-02-16 12:00 ` [PATCH 5/8] perf, tool: Add parser generator for events parsing Jiri Olsa
2012-02-16 12:00 ` [PATCH 6/8] perf, tool: Add config options support for event parsing Jiri Olsa
2012-02-16 12:00 ` [PATCH 7/8] perf, tool: Add perf pmu object to access pmu format definition Jiri Olsa
2012-02-16 12:00 ` [PATCH 8/8] perf, tool: Add support to specify pmu style event Jiri Olsa
2012-02-16 17:03 ` [PATCHv5 0/8] perf tool: parser generator for events parsing Peter Zijlstra
2012-02-16 17:35   ` Arnaldo Carvalho de Melo [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=20120216173534.GG27941@infradead.org \
    --to=acme@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.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