From: sashiko-bot@kernel.org
To: "Matt Turner" <mattst88@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/4] alpha: stop storing the user stack pointer in pt_regs
Date: Sun, 11 Oct 2026 20:30:13 +0000 [thread overview]
Message-ID: <sashiko-outbox-167450@kernel.org> (raw)
In-Reply-To: <20261011-alpha-perf-regs-v3-v1-2-eaa625a39712@gmail.com>
> Nothing reads pt_regs->usp now that user_stack_pointer() uses the PCB.
> Drop the stores, which saves a PAL_rdusp call on every syscall, and
> give the field back its old name.
>
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Matt Turner <mattst88@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261011-alpha-perf-regs-v3-v1-0-eaa625a39712@gmail.com?part=2
next prev parent reply other threads:[~2026-10-11 20:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 20:16 [PATCH 0/4] alpha: perf register sampling and user stack dumps Matt Turner
2026-10-11 20:16 ` [PATCH 1/4] alpha: fix stale user_stack_pointer() Matt Turner
2026-10-11 20:32 ` sashiko-bot
2026-10-12 16:18 ` Magnus Lindholm
2026-10-11 20:16 ` [PATCH 2/4] alpha: stop storing the user stack pointer in pt_regs Matt Turner
2026-10-11 20:30 ` sashiko-bot [this message]
2026-10-12 16:20 ` Magnus Lindholm
2026-10-11 20:16 ` [PATCH 3/4] alpha: use user_stack_pointer() in KSTK_ESP() and dump_elf_thread() Matt Turner
2026-10-11 20:31 ` sashiko-bot
2026-10-12 17:12 ` Magnus Lindholm
2026-10-11 20:16 ` [PATCH 4/4] alpha: add HAVE_PERF_REGS and HAVE_PERF_USER_STACK_DUMP support Matt Turner
2026-10-11 20:25 ` sashiko-bot
2026-10-12 17:34 ` Magnus Lindholm
2026-10-11 21:47 ` [PATCH 0/4] alpha: perf register sampling and user stack dumps Ian Rogers
2026-10-12 15:51 ` Magnus Lindholm
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=sashiko-outbox-167450@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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