linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Steve Clevenger <scclevenger@os.amperecomputing.com>
Cc: leo.yan@arm.com, 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 V8 0/4] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset
Date: Mon, 7 Oct 2024 22:51:41 -0700	[thread overview]
Message-ID: <ZwTIbRbAX2EX31X8@google.com> (raw)
In-Reply-To: <cover.1725667397.git.scclevenger@os.amperecomputing.com>

Hello,

Sorry for the long delay.  But can you please explain your problem in
more detail?  Showing ELF program (or section) header would be helpful
as well.

Is the problem when the text mapping has non-zero pgoff only?  Is the
kernel symbols working correctly?  Or is it just the Python script
broken?

Thanks,
Namhyung

On Mon, Sep 09, 2024 at 03:30:02PM -0600, Steve Clevenger wrote:
> Changes in V8:
>   - in arm-cs-trace-disasm.py, ensure map_pgoff is not converted to
>     string.
>   - Remove map_pgoff integer conversion in dso not found print
>     message.
> 
> Changes in V7:
>   - In arm-cs-trace-disasm.py, fix print message core dump resulting
>     from mixed type arithmetic.
>   - Modify CS_ETM_TRACE_ON filter to filter zero start_addr. The
>     CS_ETM_TRACE_ON message is changed to print only in verbose mode.
>   - Removed verbose mode only notification for start_addr/stop_addr
>     outside of dso address range.
> 
> Changes in V6:
>   - In arm-cs-trace-disasm.py, zero map_pgoff for kernel files. Add
>     map_pgoff to start/end address for dso not found message.
>   - Added "Reviewed-by" trailer for patches 1-3 previously reviewed
>     by Leo Yan in V4 and V5.
> 
> Changes in V5:
>   - In symbol-elf.c, branch to exit_close label if open file.
>   - In trace_event_python.c, correct indentation. set_sym_in_dict
>     call parameter "map_pgoff" renamed as "addr_map_pgoff" to
>     match local naming.
> 
> Changes in V4:
>   - In trace-event-python.c, fixed perf-tools-next merge problem.
> 
> Changes in V3:
>   - Rebased to linux-perf-tools branch.
>   - Squash symbol-elf.c and symbol.h into same commit.
>   - In map.c, merge dso__is_pie() call into existing if statement.
>   - In arm-cs-trace-disasm.py, remove debug artifacts.
> 
> Changes in V2:
>   - In dso__is_pie() (symbol-elf.c), Decrease indentation, add null pointer
>     checks per Leo Yan review.
>   - Updated mailing list distribution.
> 
> Steve Clevenger (4):
>   Add dso__is_pie call to identify ELF PIE
>   Force MAPPING_TYPE__IDENTIY for PIE
>   Add map pgoff to python dictionary based on MAPPING_TYPE
>   Adjust objdump start/end range per map pgoff parameter
> 
>  .../scripts/python/arm-cs-trace-disasm.py     | 17 ++++--
>  tools/perf/util/map.c                         |  4 +-
>  .../scripting-engines/trace-event-python.c    | 13 +++-
>  tools/perf/util/symbol-elf.c                  | 61 +++++++++++++++++++
>  tools/perf/util/symbol.h                      |  1 +
>  5 files changed, 86 insertions(+), 10 deletions(-)
> 
> -- 
> 2.44.0
> 

  parent reply	other threads:[~2024-10-08  5:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 21:30 [PATCH V8 0/4] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset Steve Clevenger
2024-09-09 21:29 ` [PATCH V8 4/4] Adjust objdump start/end range per map pgoff parameter Steve Clevenger
2024-09-10  8:03   ` Leo Yan
2024-09-09 21:29 ` [PATCH V8 3/4] Add map pgoff to python dictionary based on MAPPING_TYPE Steve Clevenger
2024-09-09 21:30 ` [PATCH V8 2/4] Force MAPPING_TYPE__IDENTIY for PIE Steve Clevenger
2024-09-09 21:30 ` [PATCH V8 1/4] Add dso__is_pie call to identify ELF PIE Steve Clevenger
2024-10-09 21:13   ` Leo Yan
2024-10-10 16:30     ` Steve Clevenger
2024-10-08  5:51 ` Namhyung Kim [this message]
2024-10-08 18:24   ` [PATCH V8 0/4] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset Steve Clevenger
2024-10-08 21:00     ` Namhyung Kim
2024-10-08 22:12       ` Steve Clevenger
2024-10-09 15:24       ` Leo Yan
2024-10-10  0:20         ` Namhyung Kim

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=ZwTIbRbAX2EX31X8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).