tree 26165f0494afe4d7d76a709daa69cb0ac960d9e5
parent a225cdd263f340c864febb1992802fb5b08bc328
author Steven Rostedt <srostedt@redhat.com> 1232080811 -0500
committer Ingo Molnar <mingo@elte.hu> 1232104689 +0100

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>