2012/8/8 Namhyung Kim <[email protected]>: >> >> $ ./perf record -e sched:sched_stat_sleep -e sched:sched_switch \ >> -e sched:sched_process_exit -gP -o ~/perf.data.raw ~/foo
Actually this string is not completed, because sched:sched_switch should be filtered by state. >> [ perf record: Woken up 1 times to write data ] >> [ perf record: Captured and wrote 0.015 MB /root/perf.data.raw (~661 >> samples) ] >> $ ./perf inject -v -s -i ~/perf.data.raw -o ~/perf.data >> $ ./perf report -i ~/perf.data > > The usage like this is too specific and hard to use IMHO. How about > putting it somehow into perf sched or new command? > > /me don't have an idea though. :-) > I'm going to add a script, so the usage will look like this: $ perf script record sched-stat -e sched:sched_stat_sleep <command> This command will collect sched_stat_* and proper sched_switch events $ perf script report sched-stat -- 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/
