From: Steve Clevenger <scclevenger@os.amperecomputing.com>
To: james.clark@linaro.org, mike.leach@linaro.org
Cc: suzuki.poulose@arm.com, leo.yan@arm.com,
ilkka@os.amperecomputing.com, coresight@lists.linaro.org,
linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 0/4] arm-cs-trace-disasm.py/perf must accommodate non-zero DSO text offset
Date: Tue, 27 Aug 2024 23:09:40 -0600 [thread overview]
Message-ID: <cover.1724820993.git.scclevenger@os.amperecomputing.com> (raw)
In-Reply-To: <cover.1724820993.git.scclevenger@os.amperecomputing.com>
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 | 9 ++-
tools/perf/util/map.c | 4 +-
.../scripting-engines/trace-event-python.c | 13 +++-
tools/perf/util/symbol-elf.c | 60 +++++++++++++++++++
tools/perf/util/symbol.h | 1 +
5 files changed, 79 insertions(+), 8 deletions(-)
--
2.25.1
next parent reply other threads:[~2024-08-28 5:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 5:09 Steve Clevenger [this message]
2024-08-28 5:09 ` [PATCH V4 4/4] Adjust objdump start/end range per map pgoff parameter Steve Clevenger
2024-08-28 8:46 ` Leo Yan
2024-08-28 5:09 ` [PATCH V4 3/4] Add map pgoff to python dictionary based on MAPPING_TYPE Steve Clevenger
2024-08-28 8:44 ` Leo Yan
2024-08-28 21:26 ` Steve Clevenger
2024-08-28 5:09 ` [PATCH V4 2/4] Force MAPPING_TYPE__IDENTIY for PIE Steve Clevenger
2024-08-28 8:26 ` Leo Yan
2024-08-28 5:09 ` [PATCH V4 1/4] Add dso__is_pie call to identify ELF PIE Steve Clevenger
2024-08-28 8:23 ` Leo Yan
2024-08-28 15:48 ` Steve Clevenger
2024-08-28 20:34 ` Leo Yan
2024-08-28 20:36 ` 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=cover.1724820993.git.scclevenger@os.amperecomputing.com \
--to=scclevenger@os.amperecomputing.com \
--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=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).