latency-tracing-v2.6.16
From: | Ingo Molnar <mingo@elte.hu> | |
To: | linux-kernel@vger.kernel.org | |
Subject: | [patch] latency-tracing-v2.6.16 | |
Date: | Mon, 20 Mar 2006 11:13:07 +0100 |
i've released the latency-tracer patch for v2.6.16: http://redhat.com/~mingo/latency-tracing-patches/latency-... max scheduling latencies can be tracked via the enabling of CONFIG_WAKEUP_TIMING. Tracking can be started via the resetting of the max latency: echo 0 > /proc/sys/kernel/preempt_max_latency if CONFIG_LATENCY_TRACE is enabled too then an execution trace will be automatically generated as well, accessible via /proc/latency_trace. if CONFIG_DEBUG_STACKOVERFLOW is enabled too then the function tracer will also track the maximum stack-footprint observed in the system, on a per-function-call basis. New maximums are reported to the syslog immediately. (which can be quite verbose during bootup.) (the latency-tracer has numerous other features as well, such as userspace-triggered kernel-tracing, irq-triggered tracing, max preempt-off or irq-off tracing, trace-to-console-via-early-printk for the debugging of early bootup crashes, print-trace-at-crash, and more. See past postings and the code for details.) Ingo - 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/