git://ftp.safe.ca / safe / jmp / linux-2.6 / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 41dfba4) | patch
tracing: do not update tracing_max_latency when tracer is stopped
authorCarsten Emde <Carsten.Emde@osadl.org>
Sat, 12 Sep 2009 23:43:07 +0000 (01:43 +0200)
committerSteven Rostedt <rostedt@goodmis.org>
Sun, 13 Sep 2009 01:45:17 +0000 (21:45 -0400)
commitb5130b1e7d3717d03ab1916b198bf0d49fa0a619
tree67ee3282f6b6aa2e37864b938f67fd7e02b04394tree | snapshot
parent41dfba4367109b92d92ec6e059be6950497d932fcommit | diff
tracing: do not update tracing_max_latency when tracer is stopped

The state of the function pair tracing_stop()/tracing_start() is
correctly considered when tracer data are updated. However, the global
and externally accessible variable tracing_max_latency is always updated
- even when tracing is stopped.

The update should only occur, if tracing was not stopped.

Signed-off-by: Carsten Emde <C.Emde@osadl.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/trace.c diff | blob | history
kernel/trace/trace.h diff | blob | history
kernel/trace/trace_irqsoff.c diff | blob | history
kernel/trace/trace_sched_wakeup.c diff | blob | history
Full containers within linux kernel