From: Athira Rajeev <atrajeev@linux.ibm.com>
To: acme@kernel.org, jolsa@kernel.org, adrian.hunter@intel.com,
maddy@linux.ibm.com, irogers@google.com, namhyung@kernel.org
Cc: linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
atrajeev@linux.ibm.com, hbathini@linux.vnet.ibm.com,
tejas05@linux.ibm.com, tshah@linux.ibm.com,
venkat88@linux.ibm.com, narnalli@in.ibm.com, vpuliyal@in.ibm.com
Subject: [PATCH] perf disasm powerpc: handle Power10 prefixed instruction continuation lines
Date: Mon, 7 Sep 2026 10:44:29 +0530 [thread overview]
Message-ID: <20260907051429.29080-1-atrajeev@linux.ibm.com> (raw)
Power10 introduces prefixed instructions that are 8 bytes wide. objdump
emits these as two lines: the first carries both the raw bytes and the
mnemonic, while the second carries only the raw bytes of the second word
with no mnemonic:
1020900c: 0b 00 10 06 pla r31,757280 # 102c1e2c <cctki_vi_ML_CCZ4>
10209010: 20 8e e0 3b
disasm_line__parse_powerpc() calls disasm_line__parse() on the mnemonic
portion of the line. disasm_line__parse() returns -1 when the name
string is empty, which causes disasm_line__new() to return NULL, which
causes symbol__parse_objdump_line() to return -1, which immediately
breaks the objdump output parsing loop in symbol__disassemble_objdump().
The result is that annotation of any function containing a prefixed
instruction stops at the continuation word and all subsequent
instructions in the function are lost.
Fix this by treating an empty mnemonic as a valid case in
disasm_line__parse_powerpc(): skip the call to disasm_line__parse() and
set the instruction name to an empty heap-allocated string instead,
allowing parsing to continue to the next line.
Reported-by: Narendra Nalli <narnalli@in.ibm.com>
Reported-by: Vijay Puliyala <vpuliyal@in.ibm.com>
Signed-off-by: Athira Rajeev <atrajeev@linux.ibm.com>
---
tools/perf/util/disasm.c | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/disasm.c b/tools/perf/util/disasm.c
index e263a2a8715d..8dca703a5c74 100644
--- a/tools/perf/util/disasm.c
+++ b/tools/perf/util/disasm.c
@@ -884,10 +884,24 @@ static int disasm_line__parse_powerpc(struct disasm_line *dl, struct annotate_ar
if (name_raw_insn[0] == '\0')
return -1;
- if (disasm)
- ret = disasm_line__parse(name, namep, rawp);
- else
+ if (disasm) {
+ /*
+ * Power10 prefixed instructions are 8 bytes and objdump emits
+ * the second word on its own line with raw bytes but no
+ * mnemonic, e.g.:
+ * 1020900c: 0b 00 10 06 pla r31,757280
+ * 10209010: 20 8e e0 3b
+ *
+ * Treat a missing mnemonic as an empty instruction name rather
+ * than a parse failure, so that parsing continues past it.
+ */
+ if (name[0] != '\0')
+ ret = disasm_line__parse(name, namep, rawp);
+ else
+ *namep = strdup("");
+ } else {
*namep = "";
+ }
tmp_raw_insn = strndup(name_raw_insn, 11);
if (tmp_raw_insn == NULL)
--
2.43.0
next reply other threads:[~2026-09-07 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 5:14 Athira Rajeev [this message]
2026-09-07 5:30 ` [PATCH] perf disasm powerpc: handle Power10 prefixed instruction continuation lines sashiko-bot
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=20260907051429.29080-1-atrajeev@linux.ibm.com \
--to=atrajeev@linux.ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=namhyung@kernel.org \
--cc=narnalli@in.ibm.com \
--cc=tejas05@linux.ibm.com \
--cc=tshah@linux.ibm.com \
--cc=venkat88@linux.ibm.com \
--cc=vpuliyal@in.ibm.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