summaryrefslogtreecommitdiffstats
path: root/kernel/trace/trace_irqsoff.c
diff options
context:
space:
mode:
authorCarsten Emde <Carsten.Emde@osadl.org>2009-09-13 01:43:07 +0200
committerSteven Rostedt <rostedt@goodmis.org>2009-09-12 21:45:17 -0400
commitb5130b1e7d3717d03ab1916b198bf0d49fa0a619 (patch)
tree67ee3282f6b6aa2e37864b938f67fd7e02b04394 /kernel/trace/trace_irqsoff.c
parent41dfba4367109b92d92ec6e059be6950497d932f (diff)
downloadop-kernel-dev-b5130b1e7d3717d03ab1916b198bf0d49fa0a619.zip
op-kernel-dev-b5130b1e7d3717d03ab1916b198bf0d49fa0a619.tar.gz
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>
Diffstat (limited to 'kernel/trace/trace_irqsoff.c')
-rw-r--r--kernel/trace/trace_irqsoff.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/kernel/trace/trace_irqsoff.c b/kernel/trace/trace_irqsoff.c
index 06f8ea9..3aa7eaa 100644
--- a/kernel/trace/trace_irqsoff.c
+++ b/kernel/trace/trace_irqsoff.c
@@ -157,8 +157,10 @@ check_critical_timing(struct trace_array *tr,
data->critical_end = parent_ip;
- tracing_max_latency = delta;
- update_max_tr_single(tr, current, cpu);
+ if (likely(!is_tracing_stopped())) {
+ tracing_max_latency = delta;
+ update_max_tr_single(tr, current, cpu);
+ }
max_sequence++;
OpenPOWER on IntegriCloud