Bug#481684: Please enable CONFIG_LATENCYTOP so we can use the latencytop tool
severity 481684 wishlist
tags 481684 wontfix
thanks
On Sun, May 18, 2008 at 12:03:32AM +0200, Uwe Hermann wrote:
> please consider enabling CONFIG_LATENCYTOP in the kernel, as it's needed
> for the 'latencytop' utility to work. latencytop itself is already in
> unstable. See also http://latencytop.org/.
Latencytop support needs too much debug-only features. As we don't build
debug images, this is wontfix for now.
| config LATENCYTOP
| bool "Latency measuring infrastructure"
| select FRAME_POINTER if !MIPS
| select KALLSYMS
| select KALLSYMS_ALL
| select STACKTRACE
| select SCHEDSTATS
| select SCHED_DEBUG
> I must admit I do _not_ know if there are any negative effects when
> enabling that setting. However, I have rebuilt my kernel
> (Debian 2.6.25-3 version) with CONFIG_LATENCYTOP and it _did_ make
> latencytop work fine for me.
You should check the complete config for differences.
Bastian
--
If some day we are defeated, well, war has its fortunes, good and bad.
-- Commander Kor, "Errand of Mercy", stardate 3201.7
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
