Re: A problem about 'perf sched latency'

2018-02-07 Thread Du, Changbin
On Thu, Feb 08, 2018 at 09:57:24AM +0900, Namhyung Kim wrote: > Hello, > [snip] > > Does anyone know why? Thank you! :) > > It seems your data doesn't have wakeup event which is required by the > 'perf sched latency'. > > Thanks, > Namhyung > Hi Kim, Thanks for your reply. I thought the

Re: A problem about 'perf sched latency'

2018-02-07 Thread Du, Changbin
On Thu, Feb 08, 2018 at 09:57:24AM +0900, Namhyung Kim wrote: > Hello, > [snip] > > Does anyone know why? Thank you! :) > > It seems your data doesn't have wakeup event which is required by the > 'perf sched latency'. > > Thanks, > Namhyung > Hi Kim, Thanks for your reply. I thought the

Re: A problem about 'perf sched latency'

2018-02-07 Thread Namhyung Kim
Hello, On Tue, Feb 06, 2018 at 09:50:02PM +0800, Du, Changbin wrote: > Hello all, > I am using perf sched tool to analyzer sched data on my machine. But it seems > that > 'perf sched latency' report incorrect 'Switches'. What I did is as below. > > First, record... > $ sudo perf sched record

Re: A problem about 'perf sched latency'

2018-02-07 Thread Namhyung Kim
Hello, On Tue, Feb 06, 2018 at 09:50:02PM +0800, Du, Changbin wrote: > Hello all, > I am using perf sched tool to analyzer sched data on my machine. But it seems > that > 'perf sched latency' report incorrect 'Switches'. What I did is as below. > > First, record... > $ sudo perf sched record

A problem about 'perf sched latency'

2018-02-06 Thread Du, Changbin
Hello all, I am using perf sched tool to analyzer sched data on my machine. But it seems that 'perf sched latency' report incorrect 'Switches'. What I did is as below. First, record... $ sudo perf sched record time pi 200 > /dev/null Then check statistics. It says 'pi' only sched-in 1

A problem about 'perf sched latency'

2018-02-06 Thread Du, Changbin
Hello all, I am using perf sched tool to analyzer sched data on my machine. But it seems that 'perf sched latency' report incorrect 'Switches'. What I did is as below. First, record... $ sudo perf sched record time pi 200 > /dev/null Then check statistics. It says 'pi' only sched-in 1