diff options
| author |   Steven Rostedt (Google) <rostedt@goodmis.org> | 2023-12-05 16:52:11 -0500 |
|---|---|---|
| committer | Steven Rostedt (Google) <rostedt@goodmis.org> | 2023-12-05 17:06:12 -0500 |
| commit | b538bf7d0ec11ca49f536dfda742a5f6db90a798 (patch) | |
| tree | cd227a8e732506b530add0c52b9a39923339a06d /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | tracing: Stop current tracer when resizing buffer (diff) | |
| download | wireguard-linux-b538bf7d0ec11ca49f536dfda742a5f6db90a798.tar.xz wireguard-linux-b538bf7d0ec11ca49f536dfda742a5f6db90a798.zip | |
tracing: Disable snapshot buffer when stopping instance tracers
It use to be that only the top level instance had a snapshot buffer (for
latency tracers like wakeup and irqsoff). When stopping a tracer in an
instance would not disable the snapshot buffer. This could have some
unintended consequences if the irqsoff tracer is enabled.
Consolidate the tracing_start/stop() with tracing_start/stop_tr() so that
all instances behave the same. The tracing_start/stop() functions will
just call their respective tracing_start/stop_tr() with the global_array
passed in.
Link: https://lkml.kernel.org/r/20231205220011.041220035@goodmis.org
Cc: stable@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Fixes: 6d9b3fa5e7f6 ("tracing: Move tracing_max_latency into trace_array")
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions