mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: German Gomez <german.gomez@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: James Clark <james.clark@arm.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	mark.rutland@arm.com, namhyung@kernel.org, leo.yan@linaro.org,
	Alexandre.Truong@arm.com, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH v2 1/1] perf test arm64: Test unwinding using fame-pointer (fp) mode
Date: Tue, 22 Mar 2022 13:27:52 +0000	[thread overview]
Message-ID: <cebb404f-b40c-35f9-0395-32cb28a34ab6@arm.com> (raw)
In-Reply-To: <YjjlohvNAL8lKlV+@kernel.org>


On 21/03/2022 20:52, Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 16, 2022 at 05:48:50PM +0000, German Gomez escreveu:
>> On 16/03/2022 17:30, James Clark wrote:
>>> On 16/03/2022 17:20, German Gomez wrote:
>>>> Add a shell script to check that the call-graphs generated using frame
>>>> pointers (--call-graph fp) are complete and not missing leaf functions:
>>>>
>>>>   | $ perf test 88 -v
>>>>   |  88: Check Arm64 callgraphs are complete in fp mode                  :
>>>>   | --- start ---
>>>>   | test child forked, pid 8734
>>>>   |  + Compiling test program (/tmp/test_program.Cz3yL)...
>>>>   |  + Recording (PID=8749)...
>>>>   |  + Stopping perf-record...
>>>>   | test_program.Cz
>>>>   |                  728 leaf
>>>>   |                  753 parent
>>>>   |                  76c main
>>>>   | test child finished with 0
>>>>   | ---- end ----
>>>>   | Check Arm SPE callgraphs are complete in fp mode: Ok
>>>>
>>> Ran it on N1SDP and it passes, and it fails if b9f6fbb3b2c2 isn't applied.
>> I forgot to mention in the notes that it's supposed to work with both unwinders:
>>
>> $ make                # for libunwind (default)
>> $ make NO_LIBUNWIND=1 # for libdw
> I'll add it to the cset commit log, and also will fix this:
>
> ⬢[acme@toolbox perf]$        git am ./v2_20220316_german_gomez_perf_test_arm64_test_unwinding_using_fame_pointer_fp_mode.mbx
> Applying: perf test arm64: Test unwinding using fame-pointer (fp) mode
> .git/rebase-apply/patch:72: trailing whitespace.
> # program
> warning: 1 line adds whitespace errors.
> tools/perf/tests/shell/test_arm_callgraph_fp.sh:58: trailing whitespace.
> +# program
> ⬢[acme@toolbox perf]$
>  

Thanks Arnaldo, I forgot to run the checkpatch script.

>>> Reviewed-by: James Clark <james.clark@arm.com>
>>>
>>>> Fixes: b9f6fbb3b2c2 ("perf arm64: Inject missing frames when using 'perf record --call-graph=fp'")
>>>> Suggested-by: Jiri Olsa <jolsa@kernel.org>
>>>> Signed-off-by: German Gomez <german.gomez@arm.com>

      reply	other threads:[~2022-03-22 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 17:20 German Gomez
2022-03-16 17:30 ` James Clark
2022-03-16 17:38   ` German Gomez
2022-03-16 17:48   ` German Gomez
2022-03-21 20:52     ` Arnaldo Carvalho de Melo
2022-03-22 13:27       ` German Gomez [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=cebb404f-b40c-35f9-0395-32cb28a34ab6@arm.com \
    --to=german.gomez@arm.com \
    --cc=Alexandre.Truong@arm.com \
    --cc=acme@kernel.org \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.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

all inboxes | Powered by JetHome®