Em Mon, Oct 17, 2016 at 06:57:56AM -0700, Andi Kleen escreveu:
> > What we do know about the CPU vendor event names is that they are vendor 
> > specific, 
> > and that's a pretty stable property. So my suggestion would be to simply 
> > make it:
> > 
> >     perf list vendor
> > 
> > with perhaps add aliases as well:
> > 
> >     perf list model
> >     perf list cpu-model
> > 
> > ... and 'perf list hardware' should probably also list all the vendor 
> > specific 
> > hardware events as well.
> 
> Sure can change it.
> 
> > 
> > Could we please work a bit more on making vendor specific hardware event 
> > handling 
> > more usable to people who don't care about internals?
> 
> Do you prefer fully new patches, or are incremential patches ok? 

I would like for you to base of my perf/urgent branch as of now, that
has those two patches yanked out so that the others can go thru.

Ingo, please consider pulling from the perf-urgent-for-mingo-20161017
tag, just signed and pushed, it has:

tag perf-urgent-for-mingo-20161017
Tagger: Arnaldo Carvalho de Melo <a...@redhat.com>
Date:   Mon Oct 17 11:26:10 2016 -0300

perf/urgent fixes:

- Fix handling of numa nodes in perf.data files (Jiri Olsa)

- Fix scrolling when refreshing 'perf top --tui --hierarchy' entries
  (Namhyung Kim)

- Fix building of JIT support on Ubuntu 16.04 (Anton Blanchard)

- Fix handling of events including .c and .o, that were being treated as
  BPF scripts instead of vendor ones (Wang Nan)

Signed-off-by: Arnaldo Carvalho de Melo <a...@redhat.com>

- Arnaldo

Reply via email to