From: Leo Yan <leo.yan@linaro.org>
To: Michael Petlan <mpetlan@redhat.com>
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org,
acme@redhat.com, jolsa@kernel.org, german.gomez@arm.com
Subject: Re: [PATCH] perf test: Record only user callchains
Date: Tue, 14 Jun 2022 21:17:04 +0800 [thread overview]
Message-ID: <20220614131704.GA237086@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20220614105207.26223-1-mpetlan@redhat.com>
On Tue, Jun 14, 2022 at 12:52:07PM +0200, Michael Petlan wrote:
> The testcase 'Check Arm64 callgraphs are complete in fp mode' wants to
> see the following output:
>
> 610 leaf
> 62f parent
> 648 main
>
> However, without excluding user callchains, the output might look like:
> ffffc2ff40ef1b5c arch_local_irq_enable
> ffffc2ff419d032c __schedule
> ffffc2ff419d06c0 schedule
> ffffc2ff40e4da30 do_notify_resume
> ffffc2ff40e421b0 work_pending
> 610 leaf
> 62f parent
> 648 main
>
> Adding '--user-callchains' leaves only the wanted symbols in the chain.
>
> Suggested-by: German Gomez <german.gomez@arm.com>
> Tested-by: Michael Petlan <mpetlan@redhat.com>
Since you are the patch's author, it's not necessary to add your
tested tag.
> Signed-off-by: Michael Petlan <mpetlan@redhat.com>
With addressing German's comment for "excluding kernel callchains":
Reviewed-by: Leo Yan <leo.yan@linaro.org>
> ---
> tools/perf/tests/shell/test_arm_callgraph_fp.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/shell/test_arm_callgraph_fp.sh b/tools/perf/tests/shell/test_arm_callgraph_fp.sh
> index 6ffbb27afaba..ec108d45d3c6 100755
> --- a/tools/perf/tests/shell/test_arm_callgraph_fp.sh
> +++ b/tools/perf/tests/shell/test_arm_callgraph_fp.sh
> @@ -43,7 +43,7 @@ CFLAGS="-g -O0 -fno-inline -fno-omit-frame-pointer"
> cc $CFLAGS $TEST_PROGRAM_SOURCE -o $TEST_PROGRAM || exit 1
>
> # Add a 1 second delay to skip samples that are not in the leaf() function
> -perf record -o $PERF_DATA --call-graph fp -e cycles//u -D 1000 -- $TEST_PROGRAM 2> /dev/null &
> +perf record -o $PERF_DATA --call-graph fp -e cycles//u -D 1000 --user-callchains -- $TEST_PROGRAM 2> /dev/null &
> PID=$!
>
> echo " + Recording (PID=$PID)..."
> --
> 2.18.4
>
next prev parent reply other threads:[~2022-06-14 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 10:52 [PATCH] perf test: Record only user callchains Michael Petlan
2022-06-14 12:11 ` German Gomez
2022-06-14 12:19 ` Michael Petlan
2022-06-14 19:09 ` Arnaldo Carvalho de Melo
2022-06-14 13:17 ` Leo Yan [this message]
2022-06-14 19:09 ` Arnaldo Carvalho de Melo
2022-06-15 8:14 ` Leo Yan
2022-06-15 13:21 ` German Gomez
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=20220614131704.GA237086@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=german.gomez@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@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