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 08/23] perf annotate-arm64: Implement extract_op_location() callback
Date: Tue, 11 Aug 2026 14:50:50 +0800 [thread overview]
Message-ID: <1ade663e-da3a-4cc2-bbf9-21d61384dd9b@linux.alibaba.com> (raw)
In-Reply-To: <20260808122400.2961238-9-wutengda@huaweicloud.com>
On 8/8/26 8:23 PM, Tengda Wu wrote:
> Implement the extract_op_location() callback for the arm64 architecture
> to handle its specific assembly syntax and addressing modes.
>
> The extractor handles:
> 1. Standalone immediate operands (e.g., #0x10).
> 2. Memory references with diverse addressing modes:
> - Signed offset: [base{, #imm|reg}]
> - Pre-index: [base, #imm]!
> - Post-index: [base], #imm|reg
> 3. Multi-register operands and primary/secondary register extraction.
>
> With this callback in place, 'perf annotate' can now resolve memory
> locations and register types on arm64, marking the initial enablement
> of data type profiling for this architecture.
>
> Signed-off-by: Tengda Wu <wutengda@huaweicloud.com>
> ---
> .../perf/util/annotate-arch/annotate-arm64.c | 67 +++++++++++++++++++
> tools/perf/util/annotate.h | 10 +++
> 2 files changed, 77 insertions(+)
>
> diff --git a/tools/perf/util/annotate-arch/annotate-arm64.c b/tools/perf/util/annotate-arch/annotate-arm64.c
> index 32752a3bc756..6b4f1228afa9 100644
> --- a/tools/perf/util/annotate-arch/annotate-arm64.c
> +++ b/tools/perf/util/annotate-arch/annotate-arm64.c
> @@ -287,6 +287,72 @@ static const struct ins_ops *arm64__associate_instruction_ops(struct arch *arch,
> return ops;
> }
>
> +static int extract_op_location_arm64(const struct arch *arch,
> + struct disasm_line *dl __maybe_unused,
> + const char *op_str, int op_idx __maybe_unused,
> + struct annotated_op_loc *op_loc)
> +{
> + const char *s = op_str;
> + char *p = NULL;
> +
> + if (op_str == NULL)
> + return 0;
> +
> + /* Handle standalone immediate operands (e.g., #0x10) */
> + if (*s == arch->objdump.imm_char) {
> + op_loc->offset = strtol(s + 1, &p, 0);
> + if (p && p != s + 1)
> + op_loc->imm = true;
> + return 0;
> + }
> +
> + /*
> + * Handle memory references, identify arm64 specific addressing modes.
> + * Reference: Arm Architecture Reference Manual
> + * (DDI 0487), Chapter C1.3.3: Load/store addressing modes.
> + */
> + if (*s == arch->objdump.memory_ref_char) {
> + op_loc->mem_ref = true;
> +
> + p = strchr(s, ']');
> + if (p == NULL)
> + return -1;
> +
> + /* Pre-index: [base, #imm]! */
> + if (p[1] == '!')
> + op_loc->addr_mode = PERF_ADDR_MODE_PRE_INDEX;
> + /* Post-index: [base], #imm|reg */
> + else if (p[1] == ',' &&
> + (strchr(p + 1, arch->objdump.imm_char) ||
> + arm64__is_reg(skip_spaces(p + 2))))
> + op_loc->addr_mode = PERF_ADDR_MODE_POST_INDEX;
> + /* Signed offset: [base{, #imm|reg}] */
> + else
> + op_loc->addr_mode = PERF_ADDR_MODE_SIGNED_OFFSET;
> +
> + s++;
> + }
> +
> + /* Extract the primary register */
> + op_loc->reg1 = arch__dwarf_regnum(arch, s);
> + if (op_loc->reg1 == -1)
> + return -1;
> +
> + /* Move to the next symbol of the operand, if any */
> + s = strchr(s, ',');
> + if (s == NULL)
> + return 0;
> + s = skip_spaces(s + 1);
> +
> + /* Extract secondary register or immediate offset */
> + if (op_loc->multi_regs)
> + op_loc->reg2 = arch__dwarf_regnum(arch, s);
> + else if (*s == arch->objdump.imm_char)
> + op_loc->offset = strtol(s + 1, &p, 0);
> +
> + return 0;
> +}
> +
> const struct arch *arch__new_arm64(const struct e_machine_and_e_flags *id,
> const char *cpuid __maybe_unused)
> {
> @@ -305,6 +371,7 @@ const struct arch *arch__new_arm64(const struct e_machine_and_e_flags *id,
> arch->objdump.memory_ref_char = '[';
> arch->objdump.imm_char = '#';
> arch->associate_instruction_ops = arm64__associate_instruction_ops;
> + arch->extract_op_location = extract_op_location_arm64;
>
> /* bl, blr */
> err = regcomp(&arm->call_insn, "^blr?$", REG_EXTENDED);
> diff --git a/tools/perf/util/annotate.h b/tools/perf/util/annotate.h
> index 11b6e4780c02..a44c933f55f5 100644
> --- a/tools/perf/util/annotate.h
> +++ b/tools/perf/util/annotate.h
> @@ -494,12 +494,21 @@ int annotate_check_args(void);
>
> int arch__dwarf_regnum(const struct arch *arch, const char *str);
>
> +enum annotated_addr_mode {
> + PERF_ADDR_MODE_NONE = 0,
> +
> + PERF_ADDR_MODE_SIGNED_OFFSET,
> + PERF_ADDR_MODE_PRE_INDEX,
> + PERF_ADDR_MODE_POST_INDEX,
> +};
> +
> /**
> * struct annotated_op_loc - Location info of instruction operand
> * @reg1: First register in the operand
> * @reg2: Second register in the operand
> * @offset: Memory access offset in the operand
> * @segment: Segment selector register
> + * @addr_mode: Addressing mode, only valid if @mem_ref is true
> * @mem_ref: Whether the operand accesses memory
> * @multi_regs: Whether the second register is used
> * @imm: Whether the operand is an immediate value (in offset)
> @@ -509,6 +518,7 @@ struct annotated_op_loc {
> int reg2;
> int offset;
> u8 segment;
> + u8 addr_mode;
> bool mem_ref;
> bool multi_regs;
> bool imm;
I've checked the addressing mode classification against DDI 0487
C1.3.3 and it looks right, including the tricky cases:
- [x1, w0, sxtw #3] correctly falls through to SIGNED_OFFSET
(no '#' after ']' and 'sxtw' is not a register);
- post-index detection handles both immediate and register
writeback forms;
- the downstream use is consistent too: post-index accesses happen
at the old base, so get_reg_index_offset() returning 0 there is
correct.
Reviewed-by: Shuai Xue <xueshuai@linux.alibaba.com>
Thanks.
Shuai
next prev parent reply other threads:[~2026-08-11 6:50 UTC|newest]
Thread overview: 40+ 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
2026-08-11 2:27 ` Tengda Wu
2026-08-11 3:25 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 02/23] perf llvm: Fix arm64 adrp instruction " Tengda Wu
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 12:23 ` [PATCH v4 04/23] perf annotate-arm64: Handle load and store instructions Tengda Wu
2026-08-08 12:23 ` [PATCH v4 05/23] perf dwarf-regs: Adapt get_dwarf_regnum() for arm64 Tengda Wu
2026-08-08 12:23 ` [PATCH v4 06/23] perf annotate: Adapt arch__dwarf_regnum() " Tengda Wu
2026-08-11 6:33 ` Shuai Xue
2026-08-11 8:16 ` Tengda Wu
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 12:23 ` [PATCH v4 08/23] perf annotate-arm64: Implement extract_op_location() callback Tengda Wu
2026-08-11 6:50 ` Shuai Xue [this message]
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-11 7:09 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 12/23] perf annotate-arm64: Enable instruction tracking support Tengda Wu
2026-08-08 12:23 ` [PATCH v4 13/23] perf annotate-arm64: Track return type after call instructions Tengda Wu
2026-08-08 12:23 ` [PATCH v4 14/23] perf annotate-arm64: Support load instruction tracking Tengda Wu
2026-08-11 7:36 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 15/23] perf annotate-arm64: Support store " Tengda Wu
2026-08-11 8:00 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 16/23] perf annotate-data: Expand type_state_reg imm_value to u64 Tengda Wu
2026-08-11 8:10 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 17/23] perf annotate-data: Track imm_value for stack variables Tengda Wu
2026-08-11 8:16 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 18/23] perf annotate-arm64: Support stack variable tracking Tengda Wu
2026-08-11 8:24 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 19/23] perf annotate-arm64: Support 'mov' instruction tracking Tengda Wu
2026-08-11 8:37 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 20/23] perf annotate-arm64: Support 'add' " Tengda Wu
2026-08-11 8:45 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 21/23] perf annotate-arm64: Support 'adrp' instruction to track global variables Tengda Wu
2026-08-11 8:50 ` Shuai Xue
2026-08-08 12:23 ` [PATCH v4 22/23] perf annotate-arm64: Support per-cpu variable access tracking Tengda Wu
2026-08-08 12:24 ` [PATCH v4 23/23] perf annotate-arm64: Support 'mrs' instruction to track 'current' pointer Tengda Wu
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=1ade663e-da3a-4cc2-bbf9-21d61384dd9b@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