From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Wu <peter@lekensteyn.nl>
Cc: Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [PATCH] docs: ftrace: clarify when tracing is disabled by the trace file
Date: Fri, 30 Aug 2019 17:51:08 -0400 [thread overview]
Message-ID: <20190830175108.0ffa6ef1@gandalf.local.home> (raw)
In-Reply-To: <20190822234823.18594-1-peter@lekensteyn.nl>
On Fri, 23 Aug 2019 00:48:23 +0100
Peter Wu <peter@lekensteyn.nl> wrote:
> The current text could mislead the user into believing that only read()
> disables tracing. Clarify that any open() call that requests read access
> disables tracing.
>
> Link: https://lkml.kernel.org/r/CAADnVQ+hU6QOC_dPmpjnuv=9g4SQEeaMEMqXOS2WpMj=q=LdiQ@mail.gmail.com
> Signed-off-by: Peter Wu <peter@lekensteyn.nl>
> ---
> Documentation/trace/ftrace.rst | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index f60079259669..965be5c9afb3 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -125,7 +125,8 @@ of ftrace. Here is a list of some of the key files:
>
> This file holds the output of the trace in a human
> readable format (described below). Note, tracing is temporarily
> - disabled while this file is being read (opened).
> + disabled when the file is open for reading. Once all readers
> + are closed, tracing is re-enabled.
>
> trace_pipe:
>
> @@ -139,8 +140,9 @@ of ftrace. Here is a list of some of the key files:
> will not be read again with a sequential read. The
> "trace" file is static, and if the tracer is not
> adding more data, it will display the same
> - information every time it is read. This file will not
> - disable tracing while being read.
> + information every time it is read. Unlike the
> + "trace" file, opening this file for reading will not
> + temporarily disable tracing.
>
> trace_options:
>
> @@ -3153,7 +3155,10 @@ different. The trace is live.
>
>
> Note, reading the trace_pipe file will block until more input is
> -added.
> +added. This is contrary to the trace file. If any process opened
> +the trace file for reading, it will actually disable tracing and
> +prevent new entries from being added. The trace_file file does
I was just about to ack this, and then I saw the above.
s/trace_file/trace_pipe/
Other than that, it looks good!
-- Steve
> +not have this limitation.
>
> trace entries
> -------------
next prev parent reply other threads:[~2019-08-30 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 23:48 [PATCH] docs: ftrace: clarify when tracing is disabled by the trace file Peter Wu
2019-08-30 21:51 ` Steven Rostedt [this message]
2019-08-31 15:35 ` [PATCH v2] " Peter Wu
2019-08-31 15:58 ` Steven Rostedt
2019-09-02 13:14 ` Jonathan Corbet
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=20190830175108.0ffa6ef1@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peter@lekensteyn.nl \
/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