From: Namhyung Kim <namhyung@kernel.org>
To: Tengda Wu <wutengda@huaweicloud.com>
Cc: 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>,
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 v2 11/16] perf annotate-arm64: Support stack variable tracking
Date: Thu, 9 Apr 2026 23:29:55 -0700 [thread overview]
Message-ID: <adiY4xJ9269L70mM@google.com> (raw)
In-Reply-To: <20260403094800.1418825-12-wutengda@huaweicloud.com>
On Fri, Apr 03, 2026 at 09:47:55AM +0000, 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.
>
> This enables the instruction tracker to 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 | 83 ++++++++++++++++++-
> 1 file changed, 80 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/annotate-arch/annotate-arm64.c b/tools/perf/util/annotate-arch/annotate-arm64.c
> index 28647a778802..f9100230c2f6 100644
> --- a/tools/perf/util/annotate-arch/annotate-arm64.c
> +++ b/tools/perf/util/annotate-arch/annotate-arm64.c
> @@ -11,6 +11,8 @@
> #include "../disasm.h"
> #include "../annotate-data.h"
> #include "../debug.h"
> +#include "../map.h"
> +#include "../symbol.h"
>
> struct arch_arm64 {
> struct arch arch;
> @@ -297,6 +299,8 @@ static void update_insn_state_arm64(struct type_state *state,
> Dwarf_Die type_die;
> u32 insn_offset = dl->al.offset;
> int sreg, dreg;
> + int fbreg = dloc->fbreg;
> + int fboff = 0;
>
> if (annotate_get_insn_location(dloc->arch, dl, &loc) < 0)
> return;
> @@ -304,17 +308,59 @@ static void update_insn_state_arm64(struct type_state *state,
> sreg = src->reg1;
> dreg = dst->reg1;
>
> + 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;
> + }
> +
> /* Memory to register transfers */
> if (!strncmp(dl->ins.name, "ld", 2)) {
> struct type_state_reg dst_tsr;
>
> - if (!has_reg_type(state, sreg) ||
> - !has_reg_type(state, dreg) ||
> - !state->regs[dreg].ok)
> + if (!has_reg_type(state, sreg))
> return;
>
> tsr = &state->regs[sreg];
> tsr->copied_from = -1;
> +
> + /* Check stack variables with offset */
> + if (sreg == fbreg || sreg == state->stack_reg) {
> + struct type_state_stack *stack;
> + int offset = src->offset - fboff;
> +
> + stack = find_stack_state(state, offset);
> + if (stack == NULL) {
> + tsr->ok = false;
> + return;
> + } else if (!stack->compound) {
> + tsr->type = stack->type;
> + tsr->kind = stack->kind;
> + tsr->offset = stack->ptr_offset;
> + 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->ok = true;
> + } else {
> + tsr->ok = false;
> + return;
> + }
> +
> + pr_debug_dtp("ldr [%x] -%#x(stack) -> reg%d",
> + insn_offset, -offset, sreg);
> + pr_debug_type_name(&tsr->type, tsr->kind);
> + return;
Any chance the stack register changes the offset with the addressing
mode? I think it should be updated regardless of the result of this
operation.
> + }
> +
> + if (!has_reg_type(state, dreg) || !state->regs[dreg].ok)
> + return;
> +
> dst_tsr = state->regs[dreg];
>
> /* Dereference the pointer if it has one */
> @@ -338,6 +384,37 @@ static void update_insn_state_arm64(struct type_state *state,
>
> /* Register to memory transfers */
> if (!strncmp(dl->ins.name, "st", 2)) {
> + /* Check stack variables with offset */
> + if (dreg == fbreg || dreg == state->stack_reg) {
> + struct type_state_stack *stack;
> + int offset = dst->offset - fboff;
> +
> + if (!has_reg_type(state, sreg) ||
> + !state->regs[sreg].ok)
> + return;
> +
> + 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);
> + } else {
> + findnew_stack_state(state, offset, tsr->kind,
> + &tsr->type, tsr->offset);
> + }
> +
> + pr_debug_dtp("str [%x] reg%d -> -%#x(stack)",
> + insn_offset, sreg, -offset);
> + if (tsr->offset != 0) {
> + pr_debug_dtp(" reg%d offset %#x ->",
> + sreg, tsr->offset);
> + }
> + pr_debug_type_name(&tsr->type, tsr->kind);
> + return;
Ditto.
Thanks,
Namhyung
> + }
> +
> /*
> * Store instructions do not change the register type,
> * but the base register must be updated for pre/post-index
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-04-10 6:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 9:47 [PATCH v2 00/16] perf arm64: Support data type profiling Tengda Wu
2026-04-03 9:47 ` [PATCH v2 01/16] perf llvm: Fix arm64 adrp instruction disassembly mismatch with objdump Tengda Wu
2026-04-03 9:47 ` [PATCH v2 02/16] perf capstone: Fix arm64 jump/adrp " Tengda Wu
2026-04-07 6:43 ` Namhyung Kim
2026-04-10 9:08 ` Tengda Wu
2026-04-03 9:47 ` [PATCH v2 03/16] perf annotate-arm64: Generalize arm64_mov__parse to support standard operands Tengda Wu
2026-04-07 6:58 ` Namhyung Kim
2026-04-03 9:47 ` [PATCH v2 04/16] perf annotate-arm64: Handle load and store instructions Tengda Wu
2026-04-07 7:09 ` Namhyung Kim
2026-04-03 9:47 ` [PATCH v2 05/16] perf annotate: Introduce extract_op_location callback for arch-specific parsing Tengda Wu
2026-04-03 9:47 ` [PATCH v2 06/16] perf dwarf-regs: Adapt get_dwarf_regnum() for arm64 Tengda Wu
2026-04-03 9:47 ` [PATCH v2 07/16] perf annotate-arm64: Implement extract_op_location() callback Tengda Wu
2026-04-07 7:26 ` Namhyung Kim
2026-04-03 9:47 ` [PATCH v2 08/16] perf annotate-arm64: Enable instruction tracking support Tengda Wu
2026-04-10 6:09 ` Namhyung Kim
2026-04-03 9:47 ` [PATCH v2 09/16] perf annotate-arm64: Support load instruction tracking Tengda Wu
2026-04-10 6:23 ` Namhyung Kim
2026-04-03 9:47 ` [PATCH v2 10/16] perf annotate-arm64: Support store " Tengda Wu
2026-04-03 9:47 ` [PATCH v2 11/16] perf annotate-arm64: Support stack variable tracking Tengda Wu
2026-04-10 6:29 ` Namhyung Kim [this message]
2026-04-03 9:47 ` [PATCH v2 12/16] perf annotate-arm64: Support 'mov' instruction tracking Tengda Wu
2026-04-10 6:39 ` Namhyung Kim
2026-04-03 9:47 ` [PATCH v2 13/16] perf annotate-arm64: Support 'add' " Tengda Wu
2026-04-10 6:42 ` Namhyung Kim
2026-04-03 9:47 ` [PATCH v2 14/16] perf annotate-arm64: Support 'adrp' instruction to track global variables Tengda Wu
2026-04-03 9:47 ` [PATCH v2 15/16] perf annotate-arm64: Support per-cpu variable access tracking Tengda Wu
2026-04-03 9:48 ` [PATCH v2 16/16] perf annotate-arm64: Support 'mrs' instruction to track 'current' pointer Tengda Wu
2026-04-10 6:52 ` Namhyung Kim
2026-04-07 6:31 ` [PATCH v2 00/16] perf arm64: Support data type profiling Namhyung Kim
2026-04-08 11:35 ` Tengda Wu
2026-04-10 7:00 ` Namhyung Kim
2026-04-10 8:17 ` 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=adiY4xJ9269L70mM@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=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=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