2012/8/8 Namhyung Kim <namhy...@kernel.org>: > On Wed, 8 Aug 2012 09:02:18 +0400, Andrey Wagin wrote: >> 2012/8/8 Namhyung Kim <namhy...@kernel.org>: >>>> >>>> $ ./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 > > ??? That means '-e sched:sched_stat_sleep' part can be removed from > command line, no?
No. My method works for all kind of sched_stat_* events, so you need to specify an event type which should be traced. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
