From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>,
coresight@lists.linaro.org, gankulkarni@os.amperecomputing.com,
mike.leach@linaro.org, suzuki.poulose@arm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Ruidong Tian <tianruidong@linux.alibaba.com>,
Benjamin Gray <bgray@linux.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf scripts python: cs-etm: Update example to provide vmlinux path to Perf
Date: Wed, 24 Jul 2024 16:00:04 +0100 [thread overview]
Message-ID: <225ff37c-0e50-48d5-bb4c-e8a63e72991a@arm.com> (raw)
In-Reply-To: <20240724143319.169745-1-james.clark@linaro.org>
On 7/24/2024 3:33 PM, James Clark wrote:
>
> The example shows the vmlinux path being given to the script, but this
> only works when running on the target. If the script is run off the
> target, then confusingly the vmlinux argument also needs to be given to
> Perf as well.
>
> Without going into too much detail in the example about when it is or
> isn't required, just include it. It doesn't do any harm even when
> running on the target. Now the example command works in both places.
>
> Signed-off-by: James Clark <james.clark@linaro.org>
The change makes senses to me. Just check a bit, does it need to add the same
option for the command "only source line and symbols"?
Thanks,
Leo
> ---
> tools/perf/scripts/python/arm-cs-trace-disasm.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/scripts/python/arm-cs-trace-disasm.py b/tools/perf/scripts/python/arm-cs-trace-disasm.py
> index 7aff02d84ffb..4aeb9b497f7a 100755
> --- a/tools/perf/scripts/python/arm-cs-trace-disasm.py
> +++ b/tools/perf/scripts/python/arm-cs-trace-disasm.py
> @@ -19,10 +19,10 @@ from perf_trace_context import perf_set_itrace_options, \
> # Below are some example commands for using this script.
> #
> # Output disassembly with objdump:
> -# perf script -s scripts/python/arm-cs-trace-disasm.py \
> +# perf script -k path/to/vmlinux -s scripts/python/arm-cs-trace-disasm.py \
> # -- -d objdump -k path/to/vmlinux
> # Output disassembly with llvm-objdump:
> -# perf script -s scripts/python/arm-cs-trace-disasm.py \
> +# perf script -k path/to/vmlinux -s scripts/python/arm-cs-trace-disasm.py \
> # -- -d llvm-objdump-11 -k path/to/vmlinux
> # Output only source line and symbols:
> # perf script -s scripts/python/arm-cs-trace-disasm.py
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-07-24 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 14:33 [PATCH] perf scripts python: cs-etm: Update example to provide vmlinux path to Perf James Clark
2024-07-24 15:00 ` Leo Yan [this message]
2024-07-24 15:23 ` James Clark
2024-07-24 15:35 ` Leo Yan
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=225ff37c-0e50-48d5-bb4c-e8a63e72991a@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgray@linux.ibm.com \
--cc=coresight@lists.linaro.org \
--cc=gankulkarni@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=tianruidong@linux.alibaba.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