Messages in this thread | | | Date | Sat, 9 Jun 2012 13:05:47 -0300 | From | Arnaldo Carvalho de Melo <> | Subject | Re: Does perf inject preserve call chain data? |
| |
Em Fri, Jun 08, 2012 at 12:52:15PM -0700, Andi Kleen escreveu: > > > > # ./perf record -a -g -o - sleep 5 |perf inject -v -b | perf report -g -i -
> Since this is a common pattern with files, but files are often slow > and too big, it would be nice if perf had a standard alias that > started this pipeline.
I think this is just a variation for perf top, no? I.e. something like:
# perf top -a -G sleep 5
Where it would figure out that since a workload was specified, it should just not be refreshing the screen every N seconds but wait till the workload to finish and then present the results, without setting up any perf.data files.
It could as well show intermediate results every N seconds, but not decay the older samples, which should be even nicer.
For workloads where there is output it could spawn another term, in the background perhaps, that the user could switch to to see the samples collected while the workload runs.
That looks like a step in the direction of more integration of the tools, i.e. record + report (top being report+refreshes) + annotate.
- Arnaldo
| |