Re: [perfmon2] updating perf tool

[Arnaldo Carvalho de Melo <acme@ghostprotocols.net>]

Em Mon, Feb 14, 2011 at 02:04:35PM -0800, Arun Sharma escreveu:
> On Mon, Feb 14, 2011 at 12:48 PM, Arnaldo Carvalho de Melo wrote

> >> Potentially, perf itself could be structured as a set of shared
> >> libraries, which are then glued together using a scripting language.

> > That is what I'm talking about, see above commit.

> Sorry, I misunderstood. Looks like a step in the right direction!

:-)

I really need to look at the efforts you made in this direction,
experimentation, as in the --timehist case, is badly needed till we get
a good set of features for easing more widespread and innovative use of
this infrastructure.

On another use case, take the 'perf script' case: as I user I keep doing:

perf probe -L somefunction
perf probe falias=somefunction:line alias=long->variable->expression
perf record -e probe:f*
perf script -g python
perf script -s perf-script.py

rinse, repeat, using the shell script history to speed things up, surely
this can be shortened, as --timehist can be detected by report as
present in a perf.data file, etc.

Finding out use cases fast paths is the end goal, I think.

- Arnaldo