From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Zheng Yejian <zhengyejian@huaweicloud.com>
Cc: Sven Schnelle <svens@linux.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] tracing: add config option for print arguments in ftrace
Date: Sun, 8 Sep 2024 22:30:48 +0900 [thread overview]
Message-ID: <20240908223048.8bd6961dbc741d971f57b5c2@kernel.org> (raw)
In-Reply-To: <69b78634-3295-c22e-c09c-e41aa4554df3@huaweicloud.com>
On Fri, 6 Sep 2024 11:36:11 +0800
Zheng Yejian <zhengyejian@huaweicloud.com> wrote:
> On 2024/9/4 14:58, Sven Schnelle wrote:
> > Add a config option to disable/enable function argument
> > printing support during runtime.
> >
> > Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
> > ---
> > kernel/trace/Kconfig | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> > index 721c3b221048..8b9b6cdf39ac 100644
> > --- a/kernel/trace/Kconfig
> > +++ b/kernel/trace/Kconfig
> > @@ -242,6 +242,18 @@ config FUNCTION_GRAPH_RETVAL
> > enable it via the trace option funcgraph-retval.
> > See Documentation/trace/ftrace.rst
> >
> > +config FUNCTION_TRACE_ARGS
> > + bool "Kernel Function Tracer Arguments"
> > + depends on HAVE_FUNCTION_ARG_ACCESS_API
> > + depends on DEBUG_INFO_BTF && BPF_SYSCALL
>
> Nice feature!
>
> Just a nit, DEBUG_INFO_BTF currently depends on BPF_SYSCALL,
> so BPF_SYSCALL may not be necessary here. This feature
> also doesn't seem to depend on bpf.
Indeed. Sven, you can check the PROBE_EVENTS_BTF_ARGS as
an example.
config PROBE_EVENTS_BTF_ARGS
depends on HAVE_FUNCTION_ARG_ACCESS_API
depends on FPROBE_EVENTS || KPROBE_EVENTS
depends on DEBUG_INFO_BTF && BPF_SYSCALL
bool "Support BTF function arguments for probe events"
Thank you,
>
> > + default n
> > + help
> > + Support recording and printing of function arguments when using
> > + the function tracer or function graph tracer. This feature is off
> > + by default, and can be enabled via the trace option func-args (for
> > + the function tracer) and funcgraph-args (for the function graph
> > + tracer).
> > +
> > config DYNAMIC_FTRACE
> > bool "enable/disable function tracing dynamically"
> > depends on FUNCTION_TRACER
>
> --
> Thanks,
> Zheng Yejian
>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-09-08 13:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 6:58 [PATCH 0/7] add function arguments to ftrace Sven Schnelle
2024-09-04 6:58 ` [PATCH 1/7] tracing: add ftrace_regs to function_graph_enter() Sven Schnelle
2024-09-04 6:58 ` [PATCH 2/7] x86/tracing: pass " Sven Schnelle
2024-09-05 8:58 ` kernel test robot
2024-09-04 6:58 ` [PATCH 3/7] s390/tracing: " Sven Schnelle
2024-09-04 6:58 ` [PATCH 4/7] Add print_function_args() Sven Schnelle
2024-09-08 15:17 ` Masami Hiramatsu
2024-09-09 3:13 ` Donglin Peng
2024-09-04 6:58 ` [PATCH 5/7] tracing: add config option for print arguments in ftrace Sven Schnelle
2024-09-06 3:36 ` Zheng Yejian
2024-09-08 13:30 ` Masami Hiramatsu [this message]
2024-09-09 8:16 ` Sven Schnelle
2024-09-09 13:56 ` Masami Hiramatsu
2024-09-04 6:59 ` [PATCH 6/7] tracing: add support for function argument to graph tracer Sven Schnelle
2024-09-05 8:05 ` kernel test robot
2024-09-05 8:36 ` kernel test robot
2024-10-04 22:40 ` Steven Rostedt
2024-10-07 6:37 ` Sven Schnelle
2024-09-04 6:59 ` [PATCH 7/7] tracing: add arguments to function tracer Sven Schnelle
2024-09-06 3:49 ` Zheng Yejian
2024-10-04 22:43 ` Steven Rostedt
2024-09-05 15:16 ` [PATCH 0/7] add function arguments to ftrace Steven Rostedt
2024-09-06 6:18 ` Sven Schnelle
2024-09-06 14:07 ` Steven Rostedt
2024-09-08 13:28 ` Masami Hiramatsu
2024-09-09 7:52 ` Sven Schnelle
2024-09-13 6:03 ` Sven Schnelle
2024-09-20 8:17 ` Masami Hiramatsu
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=20240908223048.8bd6961dbc741d971f57b5c2@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.com \
--cc=zhengyejian@huaweicloud.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
Powered by JetHome