From: Namhyung Kim <namhyung@kernel.org>
To: Tengda Wu <wutengda@huaweicloud.com>
Cc: james.clark@linaro.org, xueshuai@linux.alibaba.com,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
leo.yan@linux.dev, Li Huafei <lihuafei1@huawei.com>,
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>,
Zecheng Li <zli94@ncsu.edu>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v5 04/26] perf annotate-arm64: Handle load and store instructions
Date: Wed, 9 Sep 2026 10:58:34 -0400 [thread overview]
Message-ID: <aqF0GuN0pJ83YAob@google.com> (raw)
In-Reply-To: <37f13e322f75aa96f9cb8b71f401c9911523f8c5.1788872630.git.wutengda@huaweicloud.com>
On Tue, Sep 08, 2026 at 01:05:07PM +0000, Tengda Wu wrote:
> Add ldst_ops to handle load and store instructions in order to parse
> the data types and offsets associated with PMU events for memory access
> instructions. There are many variants of load and store instructions in
> arm64, making it difficult to match all of these instruction names
> completely. Therefore, only the instruction prefixes are matched. The
> prefix 'ld|st' covers most of the memory access instructions, 'cas|swp'
> matches atomic instructions, and 'prf' matches memory prefetch
> instructions.
>
> Signed-off-by: Li Huafei <lihuafei1@huawei.com>
> Signed-off-by: Tengda Wu <wutengda@huaweicloud.com>
Reviewed-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> .../perf/util/annotate-arch/annotate-arm64.c | 140 ++++++++++++++++++
> 1 file changed, 140 insertions(+)
>
> diff --git a/tools/perf/util/annotate-arch/annotate-arm64.c b/tools/perf/util/annotate-arch/annotate-arm64.c
> index 151184210691..a7595a954cfa 100644
> --- a/tools/perf/util/annotate-arch/annotate-arm64.c
> +++ b/tools/perf/util/annotate-arch/annotate-arm64.c
> @@ -14,6 +14,7 @@ struct arch_arm64 {
> struct arch arch;
> regex_t call_insn;
> regex_t jump_insn;
> + regex_t ldst_insn; /* load and store instruction */
> };
>
> static bool arm64__is_reg(const char *op)
> @@ -170,6 +171,130 @@ static const struct ins_ops arm64_mov_ops = {
> .scnprintf = arm64_mov__scnprintf,
> };
>
> +static bool arm64__insn_is_target_on_right(const char *ins_name)
> +{
> + /*
> + * Store instructions write to the memory operand on the right,
> + * unlike standard syntax where the target is the left operand.
> + */
> + return !strncmp(ins_name, "st", 2);
> +}
> +
> +/*
> + * This function is used to parse arm64 load/store instructions into
> + * instruction operands.
> + *
> + * Typical instructions and their parsing logic:
> + *
> + * 1. Immediate offset:
> + * ldr x2, [x0] -> target="x2", source="[x0]"
> + * ldr x2, [x0, #24] -> target="x2", source="[x0, #24]"
> + * ldp x19, x20, [sp, #16] -> target="x19, x20", source="[sp, #16]"
> + *
> + * 2. Pre-index addressing:
> + * stp x29, x30, [sp, #-64]! -> target="[sp, #-64]!", source="x29, x30"
> + *
> + * 3. Post-index addressing:
> + * str x1, [x0], #8 -> target="[x0], #8", source="x1"
> + * ldr w1, [x21], #4 -> target="w1", source="[x21], #4"
> + * ldp x29, x30, [sp], #32 -> target="x29, x30", source="[sp], #32"
> + *
> + * 4. Register offset / extension:
> + * ldr x0, [x1, w0, sxtw #3] -> target="x0", source="[x1, w0, sxtw #3]"
> + * ldr x0, [x1, x0, lsl #3] -> target="x0", source="[x1, x0, lsl #3]"
> + *
> + * 5. Atomic operations:
> + * cas w3, w1, [x0] -> target="w3, w1", source="[x0]"
> + * swp x3, x0, [x2] -> target="x3, x0", source="[x2]"
> + *
> + * 6. Prefetch memory:
> + * prfm pstl1strm, [x4] -> target="pstl1strm", source="[x4]"
> + *
> + * 7. PC-relative loads (No bracket found):
> + * ldr x0, ffff800080f40c68 <__kvm_nvhe_$d> -> Fallback to default parser
> + *
> + * Parsing strategy:
> + * Use the '[' bracket as the boundary to split the operands into left
> + * and right sides. For non-store instructions, the left side is the
> + * target and the right side is the source. For store instructions, the
> + * roles are reversed.
> + */
> +static int arm64_ldst__parse(const struct arch *arch, struct ins_operands *ops,
> + struct map_symbol *ms, struct disasm_line *dl)
> +{
> + char *raw, *s, *left, *right;
> + int ret = -1;
> +
> + raw = rstrip_space_and_comment(ops->raw, arch->objdump.comment_char);
> + if (!raw)
> + return -1;
> +
> + s = strchr(raw, arch->objdump.memory_ref_char);
> + if (!s) {
> + /* Fallback to default parser for PC-relative loads. */
> + free(raw);
> + return arm64_mov__parse(arch, ops, ms, dl);
> + }
> +
> + right = strdup(s);
> + if (!right)
> + goto out_free_raw;
> +
> + while (s > raw && *s != ',')
> + --s;
> +
> + if (s == raw)
> + goto out_free_right;
> +
> + *s = '\0';
> + left = strdup(raw);
> + *s = ',';
> + if (!left)
> + goto out_free_right;
> +
> + free(raw);
> +
> + if (arm64__insn_is_target_on_right(dl->ins.name)) {
> + ops->source.raw = left;
> + ops->source.mem_ref = false;
> +
> + ops->target.raw = right;
> + ops->target.mem_ref = true;
> + } else {
> + ops->source.raw = right;
> + ops->source.mem_ref = true;
> +
> + ops->target.raw = left;
> + ops->target.mem_ref = false;
> + }
> +
> + ops->source.multi_regs = arm64__check_multi_regs(arch, ops->source.raw);
> + ops->target.multi_regs = arm64__check_multi_regs(arch, ops->target.raw);
> +
> + return 0;
> +
> +out_free_right:
> + free(right);
> +out_free_raw:
> + free(raw);
> + return ret;
> +}
> +
> +static int arm64_ldst__scnprintf(const struct ins *ins, char *bf, size_t size,
> + struct ins_operands *ops, int max_ins_name)
> +{
> + if (arm64__insn_is_target_on_right(ins->name))
> + return scnprintf(bf, size, "%-*s %s", max_ins_name, ins->name, ops->raw);
> +
> + return scnprintf(bf, size, "%-*s %s, %s", max_ins_name, ins->name,
> + ops->target.raw, ops->source.name ?: ops->source.raw);
> +}
> +
> +static struct ins_ops arm64_ldst_ops = {
> + .parse = arm64_ldst__parse,
> + .scnprintf = arm64_ldst__scnprintf,
> +};
> +
> static const struct ins_ops *arm64__associate_instruction_ops(struct arch *arch, const char *name)
> {
> struct arch_arm64 *arm = container_of(arch, struct arch_arm64, arch);
> @@ -180,6 +305,8 @@ static const struct ins_ops *arm64__associate_instruction_ops(struct arch *arch,
> ops = &jump_ops;
> else if (!regexec(&arm->call_insn, name, 2, match, 0))
> ops = &call_ops;
> + else if (!regexec(&arm->ldst_insn, name, 2, match, 0))
> + ops = &arm64_ldst_ops;
> else if (!strcmp(name, "ret"))
> ops = &ret_ops;
> else
> @@ -205,6 +332,7 @@ const struct arch *arch__new_arm64(const struct e_machine_and_e_flags *id,
> arch->objdump.comment_char = '/';
> arch->objdump.skip_functions_char = '+';
> arch->objdump.memory_ref_char = '[';
> + arch->objdump.imm_char = '#';
> arch->associate_instruction_ops = arm64__associate_instruction_ops;
>
> /* bl, blr */
> @@ -218,8 +346,20 @@ const struct arch *arch__new_arm64(const struct e_machine_and_e_flags *id,
> if (err)
> goto out_free_call;
>
> + /*
> + * The ARM64 architecture has many variants of load/store instructions.
> + * It is quite challenging to match all of them completely. Here, we
> + * only match the prefixes of these instructions.
> + */
> + err = regcomp(&arm->ldst_insn, "^(ld|st|cas|prf|swp)",
> + REG_EXTENDED);
> + if (err)
> + goto out_free_jump;
> +
> return arch;
>
> +out_free_jump:
> + regfree(&arm->jump_insn);
> out_free_call:
> regfree(&arm->call_insn);
> out_free_arm:
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-09-09 14:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 13:05 [PATCH v5 00/26] perf arm64: Support data type profiling Tengda Wu
2026-09-08 13:05 ` [PATCH v5 01/26] perf capstone: Symbolize address operands to match objdump on arm64 Tengda Wu
2026-09-08 13:05 ` [PATCH v5 02/26] perf llvm: Fix arm64 adrp instruction disassembly mismatch with objdump Tengda Wu
2026-09-09 14:50 ` Namhyung Kim
2026-09-08 13:05 ` [PATCH v5 03/26] perf annotate-arm64: Generalize arm64_mov__parse to support more instructions Tengda Wu
2026-09-09 14:52 ` Namhyung Kim
2026-09-08 13:05 ` [PATCH v5 04/26] perf annotate-arm64: Handle load and store instructions Tengda Wu
2026-09-09 14:58 ` Namhyung Kim [this message]
2026-09-08 13:05 ` [PATCH v5 05/26] perf annotate: Normalize arch__dwarf_regnum() error return values Tengda Wu
2026-09-08 17:57 ` Ian Rogers
2026-09-09 15:00 ` Namhyung Kim
2026-09-08 13:05 ` [PATCH v5 06/26] perf annotate: Introduce extract_op_location callback for arch-specific parsing Tengda Wu
2026-09-09 15:01 ` Namhyung Kim
2026-09-08 13:05 ` [PATCH v5 07/26] perf dwarf-regs: Adapt get_dwarf_regnum() for arm64 Tengda Wu
2026-09-08 13:05 ` [PATCH v5 08/26] perf annotate: Adapt arch__dwarf_regnum() " Tengda Wu
2026-09-09 15:04 ` Namhyung Kim
2026-09-08 13:05 ` [PATCH v5 09/26] perf annotate-arm64: Implement extract_op_location() callback Tengda Wu
2026-09-08 13:05 ` [PATCH v5 10/26] perf annotate: Default to --itrace=i1i for data type profiling Tengda Wu
2026-09-09 15:38 ` Adrian Hunter
2026-09-08 13:05 ` [PATCH v5 11/26] perf arm-spe: Set default synthesized event period to 1 Tengda Wu
2026-09-08 13:05 ` [PATCH v5 12/26] perf annotate-data: Extract invalidate_reg_state() as a common helper Tengda Wu
2026-09-08 13:05 ` [PATCH v5 13/26] perf annotate-arm64: Enable instruction tracking support Tengda Wu
2026-09-08 13:05 ` [PATCH v5 14/26] perf annotate-data: Add arch_get_reg_offset helper Tengda Wu
2026-09-08 13:05 ` [PATCH v5 15/26] perf annotate-arm64: Track return type after call instructions Tengda Wu
2026-09-08 13:05 ` [PATCH v5 16/26] perf annotate-arm64: Support load instruction tracking Tengda Wu
2026-09-10 13:28 ` Tengda Wu
2026-09-08 13:05 ` [PATCH v5 17/26] perf annotate-arm64: Support store " Tengda Wu
2026-09-08 13:05 ` [PATCH v5 18/26] perf annotate-data: Expand type_state_reg imm_value to u64 Tengda Wu
2026-09-08 13:05 ` [PATCH v5 19/26] perf annotate-data: Track imm_value for stack variables Tengda Wu
2026-09-08 13:05 ` [PATCH v5 20/26] perf annotate-x86: Delete stale stack state on store of untracked register Tengda Wu
2026-09-08 13:05 ` [PATCH v5 21/26] perf annotate-arm64: Support stack variable tracking Tengda Wu
2026-09-08 13:05 ` [PATCH v5 22/26] perf annotate-arm64: Support 'mov' instruction tracking Tengda Wu
2026-09-08 13:05 ` [PATCH v5 23/26] perf annotate-arm64: Support 'add' " Tengda Wu
2026-09-08 13:06 ` [PATCH v5 24/26] perf annotate-arm64: Support 'adrp' instruction to track global variables Tengda Wu
2026-09-08 13:06 ` [PATCH v5 25/26] perf annotate-arm64: Support per-cpu variable access tracking Tengda Wu
2026-09-08 13:06 ` [PATCH v5 26/26] perf annotate-arm64: Support 'mrs' instruction to track 'current' pointer Tengda Wu
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 13:00 [PATCH v5 00/26] perf arm64: Support data type profiling Tengda Wu
2026-09-08 13:01 ` [PATCH v5 04/26] perf annotate-arm64: Handle load and store instructions 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=aqF0GuN0pJ83YAob@google.com \
--to=namhyung@kernel.org \
--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=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=wutengda@huaweicloud.com \
--cc=xueshuai@linux.alibaba.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
all inboxes | Powered by JetHome®