On Mon, 2010-05-10 at 07:31 -0700, Akemi Yagi wrote: > On Mon, May 10, 2010 at 6:46 AM, Ross Walker <rswwalker at gmail.com> wrote: > > On May 10, 2010, at 8:53 AM, JohnS <jses27 at gmail.com> wrote: > > >> You say efficiency loss. That could mean anything from the power > >> input > >> down to the kernel. It looks like that can be determined by oprofile > >> and latencytop. Latencytop will give you the millisecond time for > >> execution. As far as Oprofile maybe Ross will indeed fill us in if he > >> can. > > > > Oprofile will show where those precious latencies timings are being > > used. It of course adds latency itself, so this should be factored > > into the latency timings. > > > > It will time all kernel operations then you can drill down into > > particular modules/routines to see more granularity. > > > > Needs debug symbols to be fully useful. Can provide timings as source > > code annotations. > > I never thought someone would run oprofile with the RT kernel. I can > upload debuginfo if anyone needs it. > > Akemi Actually you need kernel-trace also in there. Trace is what is recomended by TUV. John