* [PATCH] tracing: Only benchmark the time tracepoints take if tracing is on
@ 2015-10-27 12:12 Chunyan Zhang
2015-10-28 2:28 ` Steven Rostedt
0 siblings, 1 reply; 2+ messages in thread
From: Chunyan Zhang @ 2015-10-27 12:12 UTC (permalink / raw)
To: rostedt, mingo; +Cc: linux-kernel
There's no need to record the time tracepoints take when tracing is off.
This is because:
1) We cannot see these records since ring_buffer record is off at that
moment.
2) If tracing is off and benchmark tracepoint is enabled, the time
tracepoint takes is fewer than the same situation when tracing is on,
since the tracepoints need to be wrote into ring_buffer, it would
take more time. If turn on tracing at this moment, the average and
standard deviation cannot exactly present the time that tracepoints
take to write data into ring_buffer.
Signed-off-by: Chunyan Zhang <zhang.chunyan@linaro.org>
---
kernel/trace/trace_benchmark.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_benchmark.c b/kernel/trace/trace_benchmark.c
index 40a14cb..0f109c4 100644
--- a/kernel/trace/trace_benchmark.c
+++ b/kernel/trace/trace_benchmark.c
@@ -43,7 +43,7 @@ static void trace_do_benchmark(void)
unsigned int std = 0;
/* Only run if the tracepoint is actually active */
- if (!trace_benchmark_event_enabled())
+ if (!trace_benchmark_event_enabled() || !tracing_is_on())
return;
local_irq_disable();
--
1.9.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] tracing: Only benchmark the time tracepoints take if tracing is on
2015-10-27 12:12 [PATCH] tracing: Only benchmark the time tracepoints take if tracing is on Chunyan Zhang
@ 2015-10-28 2:28 ` Steven Rostedt
0 siblings, 0 replies; 2+ messages in thread
From: Steven Rostedt @ 2015-10-28 2:28 UTC (permalink / raw)
To: Chunyan Zhang; +Cc: mingo, linux-kernel
On Tue, 27 Oct 2015 20:12:13 +0800
Chunyan Zhang <zhang.chunyan@linaro.org> wrote:
> There's no need to record the time tracepoints take when tracing is off.
> This is because:
> 1) We cannot see these records since ring_buffer record is off at that
> moment.
> 2) If tracing is off and benchmark tracepoint is enabled, the time
> tracepoint takes is fewer than the same situation when tracing is on,
> since the tracepoints need to be wrote into ring_buffer, it would
> take more time. If turn on tracing at this moment, the average and
> standard deviation cannot exactly present the time that tracepoints
> take to write data into ring_buffer.
>
Thanks! I'll add this when I get back from traveling.
-- Steve
> Signed-off-by: Chunyan Zhang <zhang.chunyan@linaro.org>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-10-28 2:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-27 12:12 [PATCH] tracing: Only benchmark the time tracepoints take if tracing is on Chunyan Zhang
2015-10-28 2:28 ` Steven Rostedt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®