From: Mark Rutland <mark.rutland@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] ftrace/selftests: Fix pid test with function graph not showing pids
Date: Wed, 5 Jun 2024 10:45:54 +0100 [thread overview]
Message-ID: <ZmAz0uEKV_9ijfSF@J2N7QTR9R3> (raw)
In-Reply-To: <20240604152550.0c01d7cd@gandalf.local.home>
On Tue, Jun 04, 2024 at 03:25:50PM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> The pid filtering test will set the pid filters and make sure that both
> function and function_graph tracing honors the filters. But the
> function_graph tracer test was failing because the PID was not being
> filtered properly. That's because the funcgraph-proc option wasn't getting
> set. Without that option the PID is not shown.
>
> Instead we get:
>
> + cat trace
> # tracer: function_graph
> #
> # CPU DURATION FUNCTION CALLS
> # | | | | | | |
> 3) ! 143.685 us | kernel_clone();
> 3) ! 127.055 us | kernel_clone();
> 1) ! 127.170 us | kernel_clone();
> 3) ! 126.840 us | kernel_clone();
>
> When we should be getting:
>
> + cat trace
> # tracer: function_graph
> #
> # CPU TASK/PID DURATION FUNCTION CALLS
> # | | | | | | | | |
> 4) bash-939 | # 1070.009 us | kernel_clone();
> 4) bash-939 | # 1116.903 us | kernel_clone();
> 5) bash-939 | ! 976.133 us | kernel_clone();
> 5) bash-939 | ! 954.012 us | kernel_clone();
>
> The test looks for the pids it is filtering and will fail if it can not
> find them. Without fungraph-proc option set, it will not be displayed and
> the test will fail.
>
> Link: https://lore.kernel.org/all/Zl9JFnzKGuUM10X2@J2N7QTR9R3/
>
> Fixes: 35b944a997e2 ("selftests/ftrace: Add function_graph tracer to func-filter-pid test")
> Reported-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Applying this makes the pid filter tests go from FAIL to PASS, so FWIW:
Tested-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> tools/testing/selftests/ftrace/test.d/ftrace/func-filter-pid.tc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/func-filter-pid.tc b/tools/testing/selftests/ftrace/test.d/ftrace/func-filter-pid.tc
> index c6fc9d31a496..8dcce001881d 100644
> --- a/tools/testing/selftests/ftrace/test.d/ftrace/func-filter-pid.tc
> +++ b/tools/testing/selftests/ftrace/test.d/ftrace/func-filter-pid.tc
> @@ -8,6 +8,7 @@
> # Also test it on an instance directory
>
> do_function_fork=1
> +do_funcgraph_proc=1
>
> if [ ! -f options/function-fork ]; then
> do_function_fork=0
> @@ -28,6 +29,7 @@ fi
>
> if [ $do_funcgraph_proc -eq 1 ]; then
> orig_value2=`cat options/funcgraph-proc`
> + echo 1 > options/funcgraph-proc
> fi
>
> do_reset() {
> --
> 2.43.0
>
prev parent reply other threads:[~2024-06-05 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 19:25 [PATCH] ftrace/selftests: Fix pid test with function graph not showing pids Steven Rostedt
2024-06-05 9:45 ` Mark Rutland [this message]
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=ZmAz0uEKV_9ijfSF@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).