From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: tracing: Add stacktrace filter command
Date: Thu, 16 Aug 2018 08:50:31 -0400 [thread overview]
Message-ID: <20180816085031.531732d3@gandalf.local.home> (raw)
In-Reply-To: <153441304709.6024.553337906391633027.stgit@devbox>
On Thu, 16 Aug 2018 18:50:47 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Add a description of stacktrace filter command.
>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Jon, want to pull this patch into your tree?
-- Steve
> ---
> Documentation/trace/ftrace.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index a20d34955333..81378a8b631e 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -2987,6 +2987,9 @@ The following commands are supported:
> command, it only prints out the contents of the ring buffer for the
> CPU that executed the function that triggered the dump.
>
> +- stacktrace:
> + When the function is hit, a stack trace is recorded.
> +
> trace_pipe
> ----------
>
next prev parent reply other threads:[~2018-08-16 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <153441301698.6024.1680500212551396320.stgit@devbox>
2018-08-16 9:50 ` [PATCH 1/2] docs: tracing: Add stacktrace filter command Masami Hiramatsu
2018-08-16 12:50 ` Steven Rostedt [this message]
2018-08-31 22:35 ` 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=20180816085031.531732d3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
/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