[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180816085031.531732d3@gandalf.local.home>
Date: Thu, 16 Aug 2018 08:50:31 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/2] docs: tracing: Add stacktrace filter command
On Thu, 16 Aug 2018 18:50:47 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:
> Add a description of stacktrace filter command.
>
> Signed-off-by: Masami Hiramatsu <mhiramat@...nel.org>
> Cc: Jonathan Corbet <corbet@....net>
> Cc: linux-doc@...r.kernel.org
Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.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
> ----------
>
Powered by blists - more mailing lists