From: Tengda Wu <wutengda@huaweicloud.com>
To: Shuai Xue <xueshuai@linux.alibaba.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 18/23] perf annotate-arm64: Support stack variable tracking
Date: Fri, 14 Aug 2026 19:44:49 +0800 [thread overview]
Message-ID: <13dba899-4ff6-45a8-a360-0fcffdb1ac89@huaweicloud.com> (raw)
In-Reply-To: <1dfbb930-e8ef-4289-b443-f831251d4445@linux.alibaba.com>
On 2026/8/11 16:24, Shuai Xue wrote:
>
>
> On 8/8/26 8:23 PM, Tengda Wu wrote:
>> Extend update_insn_state() for arm64 to track data types stored on the
>> stack. This allows 'perf annotate' to maintain type information for
>> local variables that are spilled to or loaded from stack slots.
>>
>> The implementation handles:
>>
>> 1. Stack Loads (LDR): Identify when a register is loaded from a stack
>> slot and update the register's type state based on the tracked
>> stack content or compound member types.
>>
>> 2. Stack Stores (STR): Update or create new stack state entries when
>> a tracked register type is stored to the stack.
>>
>> Similar to loads, stores also support saving one or two registers
>> (in the case of 'stp'). Therefore, propagate_store_reg_state() is
>> introduced. The overall offset calculation follows the same logic as
>> the load implementation:
>>
>> src->reg1: reg_offset = get_reg_index_offset()
>> src->reg2: reg_offset = get_reg_index_offset() + reg_size(src->reg1)
>>
>> With these changes, the instruction tracker can now follow data types
>> as they move between registers and memory, specifically for function
>> local variables and compiler-spilled values on arm64.
>>
>> Signed-off-by: Tengda Wu <wutengda@huaweicloud.com>
>> ---
>> .../perf/util/annotate-arch/annotate-arm64.c | 161 ++++++++++++++++--
>> 1 file changed, 148 insertions(+), 13 deletions(-)
>>
>> diff --git a/tools/perf/util/annotate-arch/annotate-arm64.c b/tools/perf/util/annotate-arch/annotate-arm64.c
>> index ed0f0ef2877d..6e09e9707256 100644
>> --- a/tools/perf/util/annotate-arch/annotate-arm64.c
>> +++ b/tools/perf/util/annotate-arch/annotate-arm64.c
>> @@ -407,6 +407,7 @@ static void adjust_reg_index_state(struct type_state *state,
>> * to the source struct's field offset.
>> */
>> static int propagate_load_reg_state(struct type_state *state,
>> + struct data_loc_info *dloc,
>> struct disasm_line *dl, int dreg,
>> struct annotated_op_loc *src,
>> int reg_offset, const char *insn_name)
>> @@ -416,6 +417,8 @@ static int propagate_load_reg_state(struct type_state *state,
>> Dwarf_Die type_die;
>> u32 insn_offset = dl->al.offset;
>> int sreg = src->reg1;
>> + int fbreg = dloc->fbreg;
>> + int fboff = 0;
>> if (!has_reg_type(state, dreg))
>> return -1;
>> @@ -423,7 +426,52 @@ static int propagate_load_reg_state(struct type_state *state,
>> tsr = &state->regs[dreg];
>> tsr->copied_from = -1;
>> + if (dloc->fb_cfa) {
>> + u64 ip = dloc->ms->sym->start + dl->al.offset;
>> + u64 pc = map__rip_2objdump(dloc->ms->map, ip);
>> +
>> + if (die_get_cfa(dloc->di->dbg, pc, &fbreg, &fboff) < 0)
>> + fbreg = -1;
>> + }
>> +
>> retry:
>> + /* Check stack variables with offset */
>> + if (sreg == fbreg || sreg == state->stack_reg) {
>> + struct type_state_stack *stack;
>> + int offset = sreg == fbreg ? reg_offset - fboff : reg_offset;
>> +
>> + stack = find_stack_state(state, offset);
>> + if (stack == NULL) {
>> + return -1;
>> + } else if (!stack->compound) {
>> + tsr->type = stack->type;
>> + tsr->kind = stack->kind;
>> + tsr->offset = stack->ptr_offset;
>> + tsr->imm_value = stack->imm_value;
>> + tsr->ok = true;
>> + } else if (die_get_member_type(&stack->type,
>> + offset - stack->offset,
>> + &type_die)) {
>> + tsr->type = type_die;
>> + tsr->kind = TSR_KIND_TYPE;
>> + tsr->offset = 0;
>> + tsr->imm_value = 0;
>> + tsr->ok = true;
>> + } else {
>> + return -1;
>> + }
>> +
>> + if (sreg == fbreg) {
>> + pr_debug_dtp("%s [%x] -%#x(stack) -> reg%d",
>> + insn_name, insn_offset, -offset, dreg);
>> + } else {
>> + pr_debug_dtp("%s [%x] %#x(reg%d) -> reg%d",
>> + insn_name, insn_offset, offset, sreg, dreg);
>> + }
>> + pr_debug_type_name(&tsr->type, tsr->kind);
>> + return 0;
>> + }
>> +
>> if (!has_reg_type(state, sreg) || !state->regs[sreg].ok)
>> return -1;
>> @@ -460,6 +508,7 @@ static int propagate_load_reg_state(struct type_state *state,
>> }
>> static void update_load_insn_state(struct type_state *state,
>> + struct data_loc_info *dloc,
>> struct disasm_line *dl,
>> struct annotated_op_loc *src,
>> struct annotated_op_loc *dst)
>> @@ -472,7 +521,7 @@ static void update_load_insn_state(struct type_state *state,
>> goto out_err_adjust;
>> /* Handle the first destination register */
>> - if (propagate_load_reg_state(state, dl, dst->reg1, src,
>> + if (propagate_load_reg_state(state, dloc, dl, dst->reg1, src,
>> reg_offset, insn_name))
>> goto out_err_adjust;
>> @@ -481,7 +530,7 @@ static void update_load_insn_state(struct type_state *state,
>> int reg_size = arm64__reg_size(dl->ops.target.raw);
>> if (reg_size < 0 ||
>> - propagate_load_reg_state(state, dl, dst->reg2, src,
>> + propagate_load_reg_state(state, dloc, dl, dst->reg2, src,
>> reg_offset + reg_size, insn_name))
>> goto out_err_adjust;
>> }
>> @@ -498,6 +547,100 @@ static void update_load_insn_state(struct type_state *state,
>> goto out_adjust;
>> }
>> +/*
>> + * For store insns: propagate type from @sreg to the memory location
>> + * referenced by @dreg, applying @reg_offset to the destination memory offset.
>> + */
>> +static int propagate_store_reg_state(struct type_state *state,
>> + struct data_loc_info *dloc,
>> + struct disasm_line *dl, int sreg, int dreg,
>> + int reg_offset, const char *insn_name)
>> +{
>> + struct type_state_reg *tsr;
>> + u32 insn_offset = dl->al.offset;
>> + int fbreg = dloc->fbreg;
>> + int fboff = 0;
>> +
>> + if (!has_reg_type(state, sreg) || !state->regs[sreg].ok)
>> + return -1;
>
> If an untracked register is stored into a stack slot that already
> has a tracked type, this leaves the stale entry in place - a later
> load from that slot picks up the old type. The sequence is easy to
> hit: store a tracked register, cross a call, then store a register
> that the call invalidated. The right behaviour would be to drop the
> stack entry when the source is unknown. I see x86 case 3 has the
> exact same pattern, so this probably wants a cross-arch fix rather
> than an arm64-only one.
>
Agreed. We may need to introduce a delete_stack_state() helper to drop
the stack entry when the source register is unknown.
> Also, this function always returns 0 apart from that early check,
> and the callers ignore the return value anyway. Either make it void
> or return a real status and act on it.
>
Will do.
>> +
>> + if (dloc->fb_cfa) {
>> + u64 ip = dloc->ms->sym->start + dl->al.offset;
>> + u64 pc = map__rip_2objdump(dloc->ms->map, ip);
>> +
>> + if (die_get_cfa(dloc->di->dbg, pc, &fbreg, &fboff) < 0)
>> + fbreg = -1;
>> + }
>> +
>> + /* Check stack variables with offset */
>> + if (dreg == fbreg || dreg == state->stack_reg) {
>> + struct type_state_stack *stack;
>> + int offset = dreg == fbreg ? reg_offset - fboff : reg_offset;
>> +
>> + tsr = &state->regs[sreg];
>> +
>> + stack = find_stack_state(state, offset);
>> + if (stack) {
>> + if (!stack->compound)
>> + set_stack_state(stack, offset, tsr->kind, &tsr->type,
>> + tsr->offset, tsr->imm_value);
>> + /*
>> + * If it's a compound type, it means attempting to
>> + * write to a member value of the compound type without
>> + * changing the compound type itself, so do nothing.
>> + */
>> + } else {
>> + findnew_stack_state(state, offset, tsr->kind, &tsr->type,
>> + tsr->offset, tsr->imm_value);
>> + }
>> +
>> + if (dreg == fbreg) {
>> + pr_debug_dtp("%s [%x] reg%d -> -%#x(stack)",
>> + insn_name, insn_offset, sreg, -offset);
>> + } else {
>> + pr_debug_dtp("%s [%x] reg%d -> %#x(reg%d)",
>> + insn_name, insn_offset, sreg, offset, dreg);
>> + }
>> + if (tsr->offset != 0) {
>> + pr_debug_dtp(" reg%d offset %#x ->",
>> + sreg, tsr->offset);
>> + }
>> + pr_debug_type_name(&tsr->type, tsr->kind);
>> + }
>> + /*
>> + * Ignore other transfers since it'd set a value in a struct
>> + * and won't change the type.
>> + */
>> +
>> + return 0;
>> +}
>> +
>> +static void update_store_insn_state(struct type_state *state,
>> + struct data_loc_info *dloc,
>> + struct disasm_line *dl,
>> + struct annotated_op_loc *src,
>> + struct annotated_op_loc *dst)
>> +{
>> + int reg_offset = get_reg_index_offset(dst);
>> + const char *insn_name = src->multi_regs ? "stp" : "str";
>
> This misparses the exclusive stores. For stxr w2, x1, [x0] the left
> operand is "w2, x1", so multi_regs is true and the handler treats it
> as stp: it records w2's type (the status output, possibly stale) at
> the base offset and the real data register x1 at offset + reg_size,
> and w2 - which the instruction writes - is never invalidated. stxp
> is worse since its third source register is dropped entirely.
>
> Maybe restrict the propagation to str/stp explicitly and handle the
> stxr/stlxr/stxp/stlxp family separately: their first source register
> is actually a destination and should be invalidated, with only the
> remaining register(s) propagated (or just skip propagation for them
> if that's simpler).
>
Agreed. For now, we should restrict the propagation to only apply to
regular store instructions like str/stp. I'll strengthen the instruction
matching to ensure exclusive stores are excluded.
>> + /* Handle the first source register */
>> + propagate_store_reg_state(state, dloc, dl, src->reg1, dst->reg1,
>> + reg_offset, insn_name);
>> +
>> + /* Handle the second source register (stp only) */
>> + if (src->multi_regs) {
>> + int reg_size = arm64__reg_size(dl->ops.source.raw);
>> +
>> + if (reg_size >= 0)
>> + propagate_store_reg_state(state, dloc, dl, src->reg2,
>> + dst->reg1, reg_offset + reg_size,
>> + insn_name);
>
>
> Same reg_size-from-first-register pattern as the load side, so the
> element-size caveat from that patch applies here too.
>
For store instructions, there doesn't seem to be a special element-size
instruction like ldpsw on the load side, so using the register size
should be sufficient here (please correct me if I'm wrong). That said,
I agree that renaming "reg_size" to "elem_size" would make the code
more accurate and self-explanatory. I'll update it accordingly.
Thanks,
Tengda
next prev parent reply other threads:[~2026-08-14 11:44 UTC|newest]
Thread overview: 81+ 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 13:03 ` sashiko-bot
2026-08-11 2:37 ` 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 13:05 ` sashiko-bot
2026-08-11 3:19 ` Tengda Wu
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-11 7:07 ` 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 13:12 ` sashiko-bot
2026-08-11 7:18 ` Tengda Wu
2026-08-24 21:36 ` Namhyung Kim
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-11 8:10 ` Tengda Wu
2026-08-11 6:33 ` Shuai Xue
2026-08-11 8:16 ` Tengda Wu
2026-08-24 21:39 ` Namhyung Kim
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-12 1:44 ` 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
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-12 2:28 ` Tengda Wu
2026-08-12 6:07 ` Adrian Hunter
2026-08-12 8:53 ` Tengda Wu
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 13:22 ` sashiko-bot
2026-08-12 3:09 ` 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 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-13 14:44 ` Tengda Wu
2026-08-11 7:36 ` Shuai Xue
2026-08-13 14:54 ` Tengda Wu
2026-08-24 21:44 ` Namhyung Kim
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-14 1:37 ` Tengda Wu
2026-08-11 8:00 ` Shuai Xue
2026-08-14 1:26 ` Tengda Wu
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-11 8:10 ` Shuai Xue
2026-08-14 7:58 ` Tengda Wu
2026-08-24 21:48 ` Namhyung Kim
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-08 13:25 ` sashiko-bot
2026-08-11 8:24 ` Shuai Xue
2026-08-14 11:44 ` Tengda Wu [this message]
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-11 8:37 ` Shuai Xue
2026-08-18 8:59 ` Tengda Wu
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-11 8:45 ` Shuai Xue
2026-08-19 3:04 ` Tengda Wu
2026-08-24 21:58 ` Namhyung Kim
2026-08-28 7:41 ` Tengda Wu
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 13:18 ` sashiko-bot
2026-08-31 13:07 ` Tengda Wu
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=13dba899-4ff6-45a8-a360-0fcffdb1ac89@huaweicloud.com \
--to=wutengda@huaweicloud.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=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