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 15/23] perf annotate-arm64: Support store instruction tracking
Date: Fri, 14 Aug 2026 09:26:45 +0800 [thread overview]
Message-ID: <10c30d77-9104-4825-b581-6514a0ec5010@huaweicloud.com> (raw)
In-Reply-To: <0b47de5a-b46a-4904-93a1-f6d315336a30@linux.alibaba.com>
On 2026/8/11 16:00, Shuai Xue wrote:
>
>
> On 8/8/26 8:23 PM, Tengda Wu wrote:
>> Extend update_insn_state() for arm64 to handle store (STR) instructions.
>>
>> Unlike load instructions, a store instruction sets a value in the struct
>> within the memory where the destination register resides, and does not
>> alter its type. Therefore, no processing is required for the transfer.
>>
>> The only point to note is that store instructions support pre-index and
>> post-index addressing modes, so calling adjust_reg_index_state() is still
>> necessary to handle their addressing.
>>
>> Signed-off-by: Tengda Wu <wutengda@huaweicloud.com>
>> ---
>> tools/perf/util/annotate-arch/annotate-arm64.c | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/util/annotate-arch/annotate-arm64.c b/tools/perf/util/annotate-arch/annotate-arm64.c
>> index 6557c0ad11b2..ed0f0ef2877d 100644
>> --- a/tools/perf/util/annotate-arch/annotate-arm64.c
>> +++ b/tools/perf/util/annotate-arch/annotate-arm64.c
>> @@ -560,7 +560,7 @@ static void update_insn_state_arm64(struct type_state *state,
>> * prevent stale type info from propagating to subsequent instructions.
>> */
>> if (has_reg_type(state, dst->reg1) &&
>> - strncmp(dl->ins.name, "ld", 2)) {
>> + strncmp(dl->ins.name, "ld", 2) && strncmp(dl->ins.name, "st", 2)) {
>> pr_debug_dtp("%s [%x] invalidate reg%d",
>> dl->ins.name, insn_offset, dst->reg1);
>> invalidate_reg_state(&state->regs[dst->reg1]);
>> @@ -575,6 +575,17 @@ static void update_insn_state_arm64(struct type_state *state,
>> /* Memory to register transfers */
>> if (!strncmp(dl->ins.name, "ld", 2))
>> update_load_insn_state(state, dl, src, dst);
>> + /* Register to memory transfers */
>> + else if (!strncmp(dl->ins.name, "st", 2)) {
>> + /*
>> + * Ignore transfers since it'd set a value in a struct
>> + * and won't change the type.
>> + *
>> + * Needs to update the pre-index and post-index addressing
>> + * modes for the destination register.
>> + */
>> + adjust_reg_index_state(state, dst, "str", insn_offset);
>> + }
> Two points on this call:
>
> First, adjust_reg_index_state() gets post-index with a register
> writeback amount wrong, e.g. str x1, [x0], x2. There the memory
> operand has multi_regs set (x0 and x2), so reg2 gets the offset
> register and op_loc->offset stays 0. The adjustment then degenerates
> to offset += 0, and the base keeps its old type and offset while in
> reality it moved by an unknown amount - every later access through it
> resolves to the wrong struct field. Pre-index is fine since
> [base, reg]! isn't a valid encoding, but the post-index register form
> should fall back to invalidating the base:
>
> if (op_loc->multi_regs) {
> invalidate_reg_state(tsr);
> return;
> }
>
The manual says that "[base], reg" is only used in SIMD instructions,
and since SIMD is not currently supported, the impact is limited.
However, for the sake of accuracy, I will add this check. Thank you.
> This applies to the load path too since it shares
> adjust_reg_index_state().
>
> Second, a nit: the insn name is hardcoded to "str", so stp/stlr and
> pre/post-indexed variants all print as "str" in the debug output.
> Pass dl->ins.name instead.
>
I referred to the x86 approach here (x86 also does not distinguish specific
instruction names; for example, all mov* variants are printed as "mov").
Originally, I only intended to distinguish between the two categories, ldr
and str. Of course, using the specific instruction name is not a problem,
and I will fix it accordingly.
Thanks,
Tengda
next prev parent reply other threads:[~2026-08-14 1:26 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 [this message]
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
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=10c30d77-9104-4825-b581-6514a0ec5010@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