From: Stian Halseth <stian@itx.no>
To: sashiko-reviews@lists.linux.dev
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] sparc64: Support PERF_SAMPLE_REGS_USER and PERF_SAMPLE_STACK_USER
Date: Tue, 22 Sep 2026 16:36:58 +0200 [thread overview]
Message-ID: <df43e814d5681df85bf522afae345aca0b9be5cf.camel@itx.no> (raw)
In-Reply-To: <20260922141826.CC3081F00898@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
On Tue, 2026-09-22 at 14:18 +0000, sashiko-bot@kernel.org wrote:
>
> [Severity: Medium]
> Since HAVE_PERF_USER_STACK_DUMP is selected in Kconfig, shouldn't
> there also
> be an override for perf_user_stack_pointer() here to account for
> STACK_BIAS
> on 64-bit tasks?
Nothing to override. perf_user_stack_pointer() is a plain macro in
kernel/events/internal.h. Also, I don't think we should, as long as
every consumer takes the sampled stack pointer register as the base.
sparc-aware consumers add the 2047 when they interpret the stack. Like
for example ptrace data. It would make sparc the only arch where dump
doesn't begin at the SP register.
>
> [Severity: Medium]
> Will this unconditionally truncate 64-bit kernel registers for 32-bit
> compat
> tasks?
Yes, will correct that.
Next version truncates only when user_mode(regs), the same test arm64
makes with compat_user_mode().
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-22 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 13:56 [RFC PATCH 0/2] perf: user stack dump on sparc64 needs an arch hook Stian Halseth
2026-09-22 13:56 ` [RFC PATCH 1/2] perf/core: Let an arch prepare the user stack before it is dumped Stian Halseth
2026-09-22 14:03 ` sashiko-bot
2026-09-22 13:56 ` [RFC PATCH 2/2] sparc64: Support PERF_SAMPLE_REGS_USER and PERF_SAMPLE_STACK_USER Stian Halseth
2026-09-22 14:18 ` sashiko-bot
2026-09-22 14:36 ` Stian Halseth [this message]
2026-09-22 17:04 ` [RFC PATCH 0/2] perf: user stack dump on sparc64 needs an arch hook Magnus Lindholm
2026-09-22 20:02 ` Stian Halseth
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=df43e814d5681df85bf522afae345aca0b9be5cf.camel@itx.no \
--to=stian@itx.no \
--cc=linux-perf-users@vger.kernel.org \
--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