From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@redhat.com>, kernel <kernel@axis.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: Export tracing_start() and tracing_stop()
Date: Tue, 8 Jun 2021 14:59:27 +0200 [thread overview]
Message-ID: <20210608125927.GA4095@axis.com> (raw)
In-Reply-To: <20210607091432.667ff0ba@oasis.local.home>
On Mon, Jun 07, 2021 at 03:14:32PM +0200, Steven Rostedt wrote:
> That said though, tracing_stop() is probably not what is wanted
> (unless its for a suspend to ram thing). According to the above
> description, the author really wants to use "tracing_off()" and not
> "tracing_stop()" as tracing_off() is faster and can be turned back on
> in user-space with the "tracing_on" file in tracefs, where as,
> tracing_stop() can not be. tracing_stop() needs a tracing_start() to
> get it going again.
>
> And tracing_off() is already EXPORT_SYMBOL_GPL() (as it is commonly
> used for debugging of modules). Again, it shouldn't have any in-kernel
> users in modules, because, like I stated above, it's similar to
> trace_printk() which should be removed before pushing to Linus.
>
> I'll NAK this patch for a different reason. Use tracing_off() instead.
Right, thanks, that's certainly much simpler. I'd only used
tracing_stop() before and never noticed that tracing_on can't be used to
restart tracing, probably because the kind of problems I used it for
usually resulted in the system needing a restart anyway to be usable.
next prev parent reply other threads:[~2021-06-08 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 8:01 Vincent Whitchurch
2021-06-07 8:25 ` Christoph Hellwig
2021-06-07 13:14 ` Steven Rostedt
2021-06-08 12:59 ` Vincent Whitchurch [this message]
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=20210608125927.GA4095@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=hch@infradead.org \
--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®