[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210602080118.21627-1-vincent.whitchurch@axis.com>
Date: Wed, 2 Jun 2021 10:01:18 +0200
From: Vincent Whitchurch <vincent.whitchurch@...s.com>
To: Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>
CC: <kernel@...s.com>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH] tracing: Export tracing_start() and tracing_stop()
tracing_stop() is very useful during hands-on debugging for getting the
trace to stop exactly when the problem is detected. Export this to
modules.
Personally, I haven't yet found the need to use tracing_start() from
code since I usually start tracing via tracefs, but export that too for
symmetry since it may have its uses together with tracing_stop().
Signed-off-by: Vincent Whitchurch <vincent.whitchurch@...s.com>
---
kernel/trace/trace.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index a21ef9cd2aae..5fa36f0705b7 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -2301,6 +2301,7 @@ void tracing_start(void)
out:
raw_spin_unlock_irqrestore(&global_trace.start_lock, flags);
}
+EXPORT_SYMBOL_GPL(tracing_start);
static void tracing_start_tr(struct trace_array *tr)
{
@@ -2366,6 +2367,7 @@ void tracing_stop(void)
out:
raw_spin_unlock_irqrestore(&global_trace.start_lock, flags);
}
+EXPORT_SYMBOL_GPL(tracing_stop);
static void tracing_stop_tr(struct trace_array *tr)
{
--
2.28.0
Powered by blists - more mailing lists