Frederik Himpe wrote:
quoted text
> I'm not too sure how I should use latencytop and interpret its results. I
> start latencytop, and reproduce the problem while rhythmbox is playing. It
> seems that it automatically changes the selected application in the bottom
> list after a few seconds, probably based on the CPU usage, where it
> selects most of the time either compiz or X. The upper half of latencytop
> is always empty, for all applications. In the lower half, it shows for all
> applications something like:
> 
> Process X (7972)
> Scheduler: waiting for cpu     43.5 msec         43.5 msec
> 
> Only the times differ between the different processes.

Had the same problem until just a few days ago when I figured it out mostly 
by accident.

You need to 'echo -n 1 > /proc/sys/kernel/latencytop' to enable latencytop 
tracing to get more useful info. It's something that's badly documented 
unfortunately. Make sure you disable it again when you're done so you don't 
keep the tracing overhead.
Not sure why starting the latencytop application does not enable tracing 
automatically, or at least provides an option to do so.

I also agree that the automatic switches to other apps are strange. Adding a 
particular app name or PID on the command line does not seem to have any 
effect.

Unfortunately the latencytop website also misses usage info and seems 
generally outdated as it still says that a patch to the kernel is required.

CC'ing Arjen in the hope that he can find some time to improve this.

Cheers,
FJP
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/