Re: [PATCH 11/19] perf ftrace: Add 'report' sub-command

2013-07-11 Thread Namhyung Kim
On Wed, 10 Jul 2013 16:45:39 +0200, Jiri Olsa wrote: > On Wed, Jun 26, 2013 at 04:14:14PM +0900, Namhyung Kim wrote: > > SNIP > >> >> +static int >> +__cmd_ftrace_report(struct perf_ftrace *ftrace, int argc, const char **argv) >> +{ >> +int ret = -1; >> +const char * const report_usage[]

Re: [PATCH 11/19] perf ftrace: Add 'report' sub-command

2013-07-10 Thread Jiri Olsa
On Wed, Jun 26, 2013 at 04:14:14PM +0900, Namhyung Kim wrote: SNIP > > +static int > +__cmd_ftrace_report(struct perf_ftrace *ftrace, int argc, const char **argv) > +{ > + int ret = -1; > + const char * const report_usage[] = { > + "perf ftrace report []", > + NU

[PATCH 11/19] perf ftrace: Add 'report' sub-command

2013-06-26 Thread Namhyung Kim
From: Namhyung Kim The ftrace report command is for analyzing ftrace result as usual perf report style. Internal processing of the ftrace buffer is similar to the 'show' sub-command but it synthesizes necessary information like thread, dso, map and symbol from saved trace info. It currently cou