mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Cc: <kernel@axis.com>,
	Vincent Whitchurch <vincent.whitchurch@axis.com>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH] tracing: Export tracing_start() and tracing_stop()
Date: Wed, 2 Jun 2021 10:01:18 +0200	[thread overview]
Message-ID: <20210602080118.21627-1-vincent.whitchurch@axis.com> (raw)

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@axis.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


             reply	other threads:[~2021-06-02  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  8:01 Vincent Whitchurch [this message]
2021-06-07  8:25 ` Christoph Hellwig
2021-06-07 13:14   ` Steven Rostedt
2021-06-08 12:59     ` Vincent Whitchurch
2021-06-08 13:24       ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210602080118.21627-1-vincent.whitchurch@axis.com \
    --to=vincent.whitchurch@axis.com \
    --cc=kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®