From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Tengda Wu <wutengda@huaweicloud.com>,
Namhyung Kim <namhyung@kernel.org>,
james.clark@linaro.org, Li Huafei <lihuafei1@huawei.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
leo.yan@linux.dev, Ian Rogers <irogers@google.com>,
Kim Phillips <kim.phillips@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Bill Wendling <morbo@google.com>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Zecheng Li <zli94@ncsu.edu>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v4 01/23] perf capstone: Fix arm64 jump/adrp disassembly mismatch with objdump
Date: Mon, 10 Aug 2026 21:08:34 +0800 [thread overview]
Message-ID: <1b7e48ec-66a0-4727-b533-ff87f54df057@linux.alibaba.com> (raw)
In-Reply-To: <20260808122400.2961238-2-wutengda@huaweicloud.com>
On 8/8/26 8:23 PM, Tengda Wu wrote:
> The jump and adrp instructions parsed by libcapstone currently lack
> symbolic representation and use a '#' prefix for addresses. This
> format is inconsistent with objdump's output, which causes subsequent
> parsing in jump__parse() and arm64_mov__parse() to fail.
>
> Example mismatch:
> Current: b #0xffff8000800114c8
> Fix: b ffff8000800114c8 <el0t_64_sync+0x108>
>
> Current: adrp x18, #0xffff800081f5f000
> Fix: adrp x18, ffff800081f5f000 <this_cpu_vector>
>
> Fix this by implementing extended formatting for these arm64
> instructions during symbol__disassemble_capstone(). This ensures
> the output matches objdump's expected style, including the raw
> address and the associated <symbol+offset> suffix.
>
> Signed-off-by: Tengda Wu <wutengda@huaweicloud.com>
> ---
> tools/perf/util/capstone.c | 136 +++++++++++++++++++++++++++++++++----
> tools/perf/util/disasm.c | 5 ++
> tools/perf/util/disasm.h | 1 +
> 3 files changed, 130 insertions(+), 12 deletions(-)
>
> diff --git a/tools/perf/util/capstone.c b/tools/perf/util/capstone.c
> index 74213daf8786..fb8a2bc5558f 100644
> --- a/tools/perf/util/capstone.c
> +++ b/tools/perf/util/capstone.c
> @@ -3,6 +3,7 @@
>
> #include <errno.h>
> #include <inttypes.h>
> +#include <stdlib.h>
> #include <string.h>
>
> #include <dlfcn.h>
> @@ -31,6 +32,10 @@
> #define CS_MODE_RISCVC 4
> #endif
>
> +#if CS_VERSION_MAJOR < 4
> +#define ARM64_GRP_BRANCH_RELATIVE 7
Please add a comment explaining where '7' comes from
(CS_GRP_BRANCH_RELATIVE in capstone v3), otherwise it reads like an
arbitrary magic number.
> +#endif
> +
> #ifdef LIBCAPSTONE_DLOPEN
> static void *perf_cs_dll_handle(void)
> {
> @@ -225,6 +230,12 @@ static int capstone_init(uint16_t e_machine, csh *cs_handle, bool is64, bool is_
> * on x86 by investigating instruction details.
> */
> perf_cs_option(*cs_handle, CS_OPT_DETAIL, CS_OPT_ON);
> + } else if (arch == CS_ARCH_ARM64) {
> + /*
> + * Same as x86: arm64 needs instruction details to resolve
> + * symbolic addresses.
> + */
> + perf_cs_option(*cs_handle, CS_OPT_DETAIL, CS_OPT_ON);
> }
>
> return 0;
> @@ -299,10 +310,6 @@ static void print_capstone_detail(struct cs_insn *insn, char *buf, size_t len,
> struct map *map = args->ms->map;
> struct symbol *sym;
>
> - /* TODO: support more architectures */
> - if (!arch__is_x86(args->arch))
> - return;
> -
> if (insn->detail == NULL)
> return;
>
> @@ -354,6 +361,116 @@ static void print_capstone_detail(struct cs_insn *insn, char *buf, size_t len,
> }
> }
>
> +static int print_default_format(struct cs_insn *insn, char *buf, size_t len)
> +{
> + return scnprintf(buf, len, " %-7s %s",
> + insn->mnemonic, insn->op_str);
> +}
> +
> +static void format_capstone_insn_x86(struct cs_insn *insn, char *buf,
> + size_t len, struct annotate_args *args,
> + u64 addr)
> +{
> + int printed;
> +
> + printed = print_default_format(insn, buf, len);
> + buf += printed;
> + len -= printed;
> +
> + print_capstone_detail(insn, buf, len, args, addr);
> +}
> +
> +static bool is_pc_relative_insn(struct cs_insn *insn)
> +{
> + int i;
> +
> + if (insn->id == ARM64_INS_ADR || insn->id == ARM64_INS_ADRP)
> + return true;
> +
> + if (insn->detail == NULL)
> + return false;
> +
> + for (i = 0; i < insn->detail->groups_count; i++) {
> + if (insn->detail->groups[i] == ARM64_GRP_JUMP ||
> + insn->detail->groups[i] == ARM64_GRP_CALL ||
> + insn->detail->groups[i] == ARM64_GRP_BRANCH_RELATIVE)
> + return true;
> + }
> +
> + return false;
> +}
> +
> +static void format_capstone_insn_arm64(struct cs_insn *insn, char *buf,
> + size_t len, struct annotate_args *args)
> +{
> + struct map *map = args->ms->map;
> + struct symbol *sym;
> + char *last_imm, *endptr;
> + u64 orig_addr, addr;
> + struct map *found_map = NULL;
> +
> + print_default_format(insn, buf, len);
> + /*
> + * Adjust instructions to keep the existing behavior with objdump.
> + *
> + * Example conversion:
> + * From: b #0xffff8000800114c8
> + * To: b ffff8000800114c8 <el0t_64_sync+0x108>
> + */
> + if (is_pc_relative_insn(insn)) {
> + /* Extract last immediate value as address */
> + last_imm = strrchr(buf, '#');
> + if (!last_imm)
> + return;
> +
> + orig_addr = strtoull(last_imm + 1, &endptr, 16);
> + if (endptr == last_imm + 1)
> + return;
> +
> + addr = map__objdump_2mem(map, orig_addr);
> +
> + /* Relocate map that contains the address */
> + if (dso__kernel(map__dso(map))) {
> + found_map = maps__find(map__kmaps(map), addr);
> + if (found_map == NULL)
> + return;
> + map = found_map;
> + }
> +
> + /* Convert it to map-relative address for search */
> + addr = map__map_ip(map, addr);
> +
> + sym = map__find_symbol(map, addr);
> + if (sym == NULL) {
> + map__put(found_map);
> + return;
> + }
> +
> + /* Symbolize the resolved address */
> + len = len - (last_imm - buf);
> + if (addr == sym->start) {
> + scnprintf(last_imm, len, "%"PRIx64" <%s>",
> + orig_addr, sym->name);
> + } else {
> + scnprintf(last_imm, len, "%"PRIx64" <%s+%#"PRIx64">",
> + orig_addr, sym->name, addr - sym->start);
> + }
> + map__put(found_map);
This whole sequence (objdump_2mem -> kmaps relocation -> map_ip ->
find_symbol -> scnprintf the "<sym+off>" string) is almost identical to
what print_capstone_detail() does for x86 RIP-relative operands. Could
you factor out a common helper so the two paths don't diverge over time?
Thanks.
Shuai
next prev parent reply other threads:[~2026-08-10 13:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 12:23 [PATCH v4 00/23] perf arm64: Support data type profiling Tengda Wu
2026-08-08 12:23 ` [PATCH v4 01/23] perf capstone: Fix arm64 jump/adrp disassembly mismatch with objdump Tengda Wu
2026-08-10 13:08 ` Shuai Xue [this message]
2026-08-08 12:23 ` [PATCH v4 02/23] perf llvm: Fix arm64 adrp instruction " Tengda Wu
2026-08-08 13:03 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 03/23] perf annotate-arm64: Generalize arm64_mov__parse to support more instructions Tengda Wu
2026-08-08 13:05 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 04/23] perf annotate-arm64: Handle load and store instructions Tengda Wu
2026-08-08 13:07 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 05/23] perf dwarf-regs: Adapt get_dwarf_regnum() for arm64 Tengda Wu
2026-08-08 13:12 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 06/23] perf annotate: Adapt arch__dwarf_regnum() " Tengda Wu
2026-08-08 13:07 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 07/23] perf annotate: Introduce extract_op_location callback for arch-specific parsing Tengda Wu
2026-08-08 13:11 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 08/23] perf annotate-arm64: Implement extract_op_location() callback Tengda Wu
2026-08-08 12:23 ` [PATCH v4 09/23] perf annotate: Deduplicate overlapping ARM SPE events for data type profiling Tengda Wu
2026-08-10 6:57 ` Adrian Hunter
2026-08-08 12:23 ` [PATCH v4 10/23] perf arm-spe: Set default synthesized event period to 1 Tengda Wu
2026-08-08 12:23 ` [PATCH v4 11/23] perf annotate-data: Extract invalidate_reg_state() as a common helper Tengda Wu
2026-08-08 12:23 ` [PATCH v4 12/23] perf annotate-arm64: Enable instruction tracking support Tengda Wu
2026-08-08 13:22 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 13/23] perf annotate-arm64: Track return type after call instructions Tengda Wu
2026-08-08 13:05 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 14/23] perf annotate-arm64: Support load instruction tracking Tengda Wu
2026-08-08 13:08 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 15/23] perf annotate-arm64: Support store " Tengda Wu
2026-08-08 13:11 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 16/23] perf annotate-data: Expand type_state_reg imm_value to u64 Tengda Wu
2026-08-08 13:17 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 17/23] perf annotate-data: Track imm_value for stack variables Tengda Wu
2026-08-08 12:23 ` [PATCH v4 18/23] perf annotate-arm64: Support stack variable tracking Tengda Wu
2026-08-08 13:25 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 19/23] perf annotate-arm64: Support 'mov' instruction tracking Tengda Wu
2026-08-08 13:20 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 20/23] perf annotate-arm64: Support 'add' " Tengda Wu
2026-08-08 13:14 ` sashiko-bot
2026-08-08 12:23 ` [PATCH v4 21/23] perf annotate-arm64: Support 'adrp' instruction to track global variables Tengda Wu
2026-08-08 12:23 ` [PATCH v4 22/23] perf annotate-arm64: Support per-cpu variable access tracking Tengda Wu
2026-08-08 13:18 ` sashiko-bot
2026-08-08 12:24 ` [PATCH v4 23/23] perf annotate-arm64: Support 'mrs' instruction to track 'current' pointer Tengda Wu
2026-08-08 13:20 ` 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=1b7e48ec-66a0-4727-b533-ff87f54df057@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=kim.phillips@arm.com \
--cc=leo.yan@linux.dev \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=namhyung@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=wutengda@huaweicloud.com \
--cc=zli94@ncsu.edu \
/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