From: Namhyung Kim <namhyung@kernel.org>
To: Leo Yan <leo.yan@arm.com>,
Steve Clevenger <scclevenger@os.amperecomputing.com>
Cc: james.clark@linaro.org, mike.leach@linaro.org,
suzuki.poulose@arm.com, ilkka@os.amperecomputing.com,
coresight@lists.linaro.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V9 2/2] Adjust objdump start/end range per map pgoff parameter
Date: Thu, 17 Oct 2024 11:28:06 -0700 [thread overview]
Message-ID: <ZxFXNkaoGqnax_yV@google.com> (raw)
In-Reply-To: <d9cb2018-1f68-4aa8-b795-dfbad5e1be37@arm.com>
Hi Leo,
On Thu, Oct 17, 2024 at 12:01:28PM +0100, Leo Yan wrote:
> On 10/11/24 18:17, Steve Clevenger wrote:>
> > Extract map_pgoff parameter from the dictionary, and adjust start/end
> > range passed to objdump based on the value.
> >
> > A zero start_addr is filtered to prevent output of dso address range
> > check failures. This script repeatedly sees a zero value passed
> > in for
> > start_addr = cpu_data[str(cpu) + 'addr']
> >
> > These zero values are not a new problem. The start_addr/stop_addr warning
> > clutters the instruction trace output, hence this change.
> >
> > Signed-off-by: Steve Clevenger <scclevenger@os.amperecomputing.com>
> > ---
> > tools/perf/scripts/python/arm-cs-trace-disasm.py | 16 +++++++++++-----
> > 1 file changed, 11 insertions(+), 5 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..e29a4035723c 100755
> > --- a/tools/perf/scripts/python/arm-cs-trace-disasm.py
> > +++ b/tools/perf/scripts/python/arm-cs-trace-disasm.py
> > @@ -187,6 +187,10 @@ def process_event(param_dict):
> > dso_start = get_optional(param_dict, "dso_map_start")
> > dso_end = get_optional(param_dict, "dso_map_end")
> > symbol = get_optional(param_dict, "symbol")
> > + map_pgoff = get_optional(param_dict, "map_pgoff")
> > + # check for valid map offset
> > + if (str(map_pgoff) == '[unknown]'):
> > + map_pgoff = 0
>
> I tried to apply this patch, it reports warning:
>
> Applying: Adjust objdump start/end range per map pgoff parameter
> .git/rebase-apply/patch:16: space before tab in indent.
> map_pgoff = 0
> warning: 1 line applied after fixing whitespace errors.
>
> This means it has unexpected spaces in above line.
>
>
> When applying patches, I found the prefix is missed in the subject:
>
> perf scripts python cs-etm: Adjust objdump start/end range per map pgoff parameter
It could simply be "perf script cs-etm:" but it's up to you. :)
>
> With above fixing:
>
> Reviewed-by: Leo Yan <leo.yan@arm.com>
Thanks for your review!
Steve, can you please send v10 with the fixes?
Thanks,
Namhyung
>
> > cpu = sample["cpu"]
> > ip = sample["ip"]
> > @@ -243,9 +247,10 @@ def process_event(param_dict):
> > # Record for previous sample packet
> > cpu_data[str(cpu) + 'addr'] = addr
> >
> > - # Handle CS_ETM_TRACE_ON packet if start_addr=0 and stop_addr=4
> > - if (start_addr == 0 and stop_addr == 4):
> > - print("CPU%d: CS_ETM_TRACE_ON packet is inserted" % cpu)
> > + # Filter out zero start_address. Optionally identify CS_ETM_TRACE_ON packet
> > + if (start_addr == 0):
> > + if ((stop_addr == 4) and (options.verbose == True)):
> > + print("CPU%d: CS_ETM_TRACE_ON packet is inserted" % cpu)
> > return
> >
> > if (start_addr < int(dso_start) or start_addr > int(dso_end)):
> > @@ -262,13 +267,14 @@ def process_event(param_dict):
> > # vm_start to zero.
> > if (dso == "[kernel.kallsyms]" or dso_start == 0x400000):
> > dso_vm_start = 0
> > + map_pgoff = 0
> > else:
> > dso_vm_start = int(dso_start)
> >
> > dso_fname = get_dso_file_path(dso, dso_bid)
> > if path.exists(dso_fname):
> > - print_disam(dso_fname, dso_vm_start, start_addr, stop_addr)
> > + print_disam(dso_fname, dso_vm_start, start_addr + map_pgoff, stop_addr + map_pgoff)
> > else:
> > - print("Failed to find dso %s for address range [ 0x%x .. 0x%x ]" % (dso, start_addr, stop_addr))
> > + print("Failed to find dso %s for address range [ 0x%x .. 0x%x ]" % (dso, start_addr + map_pgoff, stop_addr + map_pgoff))
> >
> > print_srccode(comm, param_dict, sample, symbol, dso)
> > --
> > 2.44.0
> >
next prev parent reply other threads:[~2024-10-17 18:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 17:17 [PATCH V9 0/2] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset Steve Clevenger
2024-11-06 23:51 ` [PATCH V10 RESEND " Steve Clevenger
2024-10-11 17:17 ` [PATCH V9 2/2] Adjust objdump start/end range per map pgoff parameter Steve Clevenger
2024-11-06 23:51 ` [PATCH V10 RESEND 2/2] perf script python: " Steve Clevenger
2024-10-17 11:01 ` [PATCH V9 2/2] " Leo Yan
2024-10-17 18:28 ` Namhyung Kim [this message]
2024-10-17 21:56 ` Leo Yan
2024-10-11 17:17 ` [PATCH V9 1/2] Add map_pgoff to python dictionary Steve Clevenger
2024-11-06 23:51 ` [PATCH V10 RESEND 1/2] perf util scripting-engines cs-etm: " Steve Clevenger
2024-10-17 10:43 ` [PATCH V9 1/2] " Leo Yan
2024-10-17 11:03 ` Leo Yan
2024-10-16 17:51 ` [PATCH V9 0/2] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset Namhyung Kim
2024-10-16 18:36 ` Steve Clevenger
2024-11-06 23:51 ` [PATCH V10 RESEND 1/2] perf util scripting-engines cs-etm: Add map_pgoff to python dictionary Steve Clevenger
2024-11-07 18:51 ` Namhyung Kim
2024-11-08 17:48 ` Steve Clevenger
2024-11-11 19:51 ` Ian Rogers
2024-11-07 14:40 ` [PATCH V10 RESEND 0/2] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset 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=ZxFXNkaoGqnax_yV@google.com \
--to=namhyung@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=ilkka@os.amperecomputing.com \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=scclevenger@os.amperecomputing.com \
--cc=suzuki.poulose@arm.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.