From: sashiko-bot@kernel.org
To: "Stian Halseth" <stian@itx.no>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH v2 3/3] perf tools: Support sparc user register samples and dwarf unwinding
Date: Tue, 22 Sep 2026 20:28:40 +0000 [thread overview]
Message-ID: <20260922202840.E3CFF1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922201507.1719668-4-stian@itx.no>
> Add the sparc perf_regs tables and the EM_SPARC/EM_SPARCV9 dispatch for
> register names, masks, ip/sp and the perf-to-DWARF register mapping,
> plus the uapi header copy.
>
> For libdw unwinding, seed DWARF registers 16-31 (%l0-%l7, %i0-%i7) from
> the register save area at the top of the stack dump: the kernel flushes
> the sampled window there, and the CFI after `save` needs %i6 and %i7 to
> find the first caller. The dump base on sparc is the biased %sp, so
> read words from the dump with memcpy rather than an aligned
> dereference.
>
> Signed-off-by: Stian Halseth <stian@itx.no>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922201507.1719668-1-stian@itx.no?part=3
next prev parent reply other threads:[~2026-09-22 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 20:15 [RFC PATCH v2 0/3] perf: sparc64 user regs and stack dump, with an arch hook Stian Halseth
2026-09-22 20:15 ` [RFC PATCH v2 1/3] perf/core: Let an arch prepare the user stack before it is dumped Stian Halseth
2026-09-22 20:23 ` sashiko-bot
2026-09-22 20:15 ` [RFC PATCH v2 2/3] sparc64: Support PERF_SAMPLE_REGS_USER and PERF_SAMPLE_STACK_USER Stian Halseth
2026-09-22 20:33 ` sashiko-bot
2026-09-22 21:42 ` Stian Halseth
2026-09-22 21:48 ` Stian Halseth
2026-09-22 20:15 ` [RFC PATCH v2 3/3] perf tools: Support sparc user register samples and dwarf unwinding Stian Halseth
2026-09-22 20:28 ` sashiko-bot [this message]
2026-09-22 20:31 ` Ian Rogers
2026-09-22 21:09 ` 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=20260922202840.E3CFF1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=stian@itx.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.