Em Wed, Nov 18, 2015 at 12:18:20PM -0700, David Ahern escreveu: > On 11/18/15 12:16 PM, William Cohen wrote: > >As a workaround can use the filtering to cut down some of data being > >recorded with:
> >export PID=<process_of_interest> > >sudo perf record -a -e sched:sched_switch --filter "next_pid == $PID || > >prev_pid == $PID" -- > >Is the following the correct thread discussing those new sched tracepoints? > >https://lkml.org/lkml/2015/6/9/513 > I believe so Right, take a look at: commit ae938802443732e77d01f8d5b52b900b9327ff30 Author: Arnaldo Carvalho de Melo <a...@redhat.com> Date: Tue Oct 6 17:46:46 2015 -0300 perf python: Support the PERF_RECORD_SWITCH event To test it check tools/perf/python/twatch.py, after following the instructions there to enable context_switch, output looks like: [root@zoo linux]# tools/perf/python/twatch.py cpu: 1, pid: 31463, tid: 31463 { type: context_switch, next_prev_pid: 31463, next_prev_tid: 31463, switch_out: 0 } cpu: 2, pid: 31463, tid: 31496 { type: context_switch, next_prev_pid: 31463, next_prev_tid: 31496, switch_out: 0 - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
