Carsten Emde b5130b1e7d 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>
2009-09-12 21:45:17 -04:00
..
2009-07-12 12:22:34 -07:00
2009-06-24 00:02:38 -04:00
2009-06-24 00:02:38 -04:00
2009-07-29 19:10:35 -07:00
2009-07-08 09:31:56 -07:00
2009-06-16 19:47:48 -07:00
2009-07-10 17:32:55 +02:00
2009-05-15 07:56:24 -05:00
2009-08-17 11:25:08 +02:00
2009-07-27 12:15:46 -07:00
2009-01-14 18:09:02 +01:00
2009-06-18 13:03:56 -07:00
2009-07-24 15:30:45 -04:00
2009-06-18 13:03:55 -07:00
2009-03-30 22:05:16 +10:30
2009-08-01 11:18:56 -07:00
2009-08-07 10:39:55 -07:00
2009-06-16 19:47:48 -07:00
2009-06-15 21:30:23 -07:00
2009-06-18 13:03:55 -07:00