Hi Arnaldo,
On Mon, 18 Nov 2013 10:57:00 -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Nov 18, 2013 at 02:34:53PM +0900, Namhyung Kim escreveu:
>> If --show-task option is given, also print internal COMM, FORK and
>> EXIT events. It would be helpful for debugging.
>
> Humm, --show-task-events is clearer albeit long :-\ With shell
> completion shouldn't be an issue tho.
Okay, will change.
>
> Also, can't we use: perf_event__fprintf_{mmap,comm,task}?
We can do it. The output will look like below if we use
perf_event__fprintf():
swapper 0 [009] 3350640.335261: sched:sched_switch:
prev_comm=swapper/9
sleep 9486 [009] 3350640.335509: PERF_RECORD_COMM: sleep:9486
sleep 9486 [009] 3350640.335806: sched:sched_stat_runtime:
comm=sleep pid=9486
firefox 2635 [003] 3350641.275896:
PERF_RECORD_FORK(2635:9487):(2635:2635)
firefox 2635 [003] 3350641.275896: sched:sched_process_fork:
comm=firefox pid=2635
sleep 9486 [009] 3350641.336009:
PERF_RECORD_EXIT(9486:9486):(9486:9486)
But I'd prefer original version below since it shows the changes more
intuitively, no?
Thanks,
Namhyung
>
>> $ perf script --show-task
>> ...
>> swapper 0 [009] 3350640.335261: sched:sched_switch:
>> prev_comm=swapper/9
>> sleep 9486 [009] 3350640.335509: comm: perf --> sleep (9486)
>> sleep 9486 [009] 3350640.335806: sched:sched_stat_runtime:
>> comm=sleep pid=9486
>> firefox 2635 [003] 3350641.275896: fork: firefox (2635 --> 9487)
>> firefox 2635 [003] 3350641.275896: sched:sched_process_fork:
>> comm=firefox pid=2635
>> sleep 9486 [009] 3350641.336009: exit: sleep (9486)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
