aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/trace/trace_sched_wakeup.c
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2009-01-15 23:40:11 -0500
committerIngo Molnar <mingo@elte.hu>2009-01-16 12:18:09 +0100
commit745b1626dd71ce9661a05ea4db57859ed5c773d2 (patch)
tree26165f0494afe4d7d76a709daa69cb0ac960d9e5 /kernel/trace/trace_sched_wakeup.c
parenta225cdd263f340c864febb1992802fb5b08bc328 (diff)
downloadmrst-s0i3-test-745b1626dd71ce9661a05ea4db57859ed5c773d2.tar.gz
mrst-s0i3-test-745b1626dd71ce9661a05ea4db57859ed5c773d2.tar.xz
mrst-s0i3-test-745b1626dd71ce9661a05ea4db57859ed5c773d2.zip
trace: set max latency variable to zero on default
Impact: trace max latencies on start of latency tracing This patch sets the max latency to zero whenever one of the irq variant tracers or the wakeup tracer is set to current tracer. Most developers expect to see output when starting up a latency tracer. But since the max_latency is already set to max, and it takes a latency greater than max_latency to be recorded, there is no trace. This is not the expected behavior and has even confused myself. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/trace/trace_sched_wakeup.c')
-rw-r--r--kernel/trace/trace_sched_wakeup.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/kernel/trace/trace_sched_wakeup.c b/kernel/trace/trace_sched_wakeup.c
index 43586b689e3..42ae1e77b6b 100644
--- a/kernel/trace/trace_sched_wakeup.c
+++ b/kernel/trace/trace_sched_wakeup.c
@@ -333,6 +333,7 @@ static void stop_wakeup_tracer(struct trace_array *tr)
static int wakeup_tracer_init(struct trace_array *tr)
{
+ tracing_max_latency = 0;
wakeup_trace = tr;
start_wakeup_tracer(tr);
return 0;