summaryrefslogtreecommitdiffstats
path: root/kernel/latencytop.c
diff options
context:
space:
mode:
authorDave Hansen <dave@linux.vnet.ibm.com>2008-10-16 07:01:46 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2008-10-16 20:21:31 +0200
commit22b8ce94708f7cdf0b04965c6f7443dfd374c35c (patch)
treee2d5b60e9b881cf251185b23c3853c8b3e52d42a /kernel/latencytop.c
parentrlimit: permit setting RLIMIT_NOFILE to RLIM_INFINITY (diff)
downloadlinux-22b8ce94708f7cdf0b04965c6f7443dfd374c35c.tar.xz
linux-22b8ce94708f7cdf0b04965c6f7443dfd374c35c.zip
profiling: dynamically enable readprofile at runtime
Way too often, I have a machine that exhibits some kind of crappy behavior. The CPU looks wedged in the kernel or it is spending way too much system time and I wonder what is responsible. I try to run readprofile. But, of course, Ubuntu doesn't enable it by default. Dang! The reason we boot-time enable it is that it takes a big bufffer that we generally can only bootmem alloc. But, does it hurt to at least try and runtime-alloc it? To use: echo 2 > /sys/kernel/profile Then run readprofile like normal. This should fix the compile issue with allmodconfig. I've compile-tested on a bunch more configs now including a few more architectures. Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com> Acked-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/latencytop.c')
0 files changed, 0 insertions, 0 deletions