All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: German Gomez <german.gomez@arm.com>
Cc: Michael Petlan <mpetlan@redhat.com>,
	linux-perf-users@vger.kernel.org, acme@redhat.com,
	jolsa@kernel.org, James Clark <james.clark@arm.com>,
	Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH] perf test: Record only user callchains
Date: Tue, 14 Jun 2022 16:09:09 -0300	[thread overview]
Message-ID: <Yqjc1W5hhnJZLGHx@kernel.org> (raw)
In-Reply-To: <7460bdf5-7c11-bfa7-9105-5b6b453aa925@arm.com>

Em Tue, Jun 14, 2022 at 01:11:20PM +0100, German Gomez escreveu:
> Hi Michael, thanks for the fix
> 
> On 14/06/2022 11:52, 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:
> 
> I think you meant "kernel callchains"

Fixed
 
> > 	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>
> > Signed-off-by: Michael Petlan <mpetlan@redhat.com>
> 
> Fixes: cd6382d82752 ("perf test arm64: Test unwinding using fame-pointer (fp) mode")
> Reviewed-by: German Gomez <german.gomez@arm.com>

Added, thanks.

- Arnaldo
 
> German
> 
> > ---
> >  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)..."

-- 

- Arnaldo

  parent reply	other threads:[~2022-06-14 19:09 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 [this message]
2022-06-14 13:17 ` Leo Yan
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=Yqjc1W5hhnJZLGHx@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=german.gomez@arm.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.