mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stian Halseth <stian@itx.no>
To: Magnus Lindholm <linmag7@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	 Andreas Larsson <andreas@gaisler.com>,
	"David S. Miller" <davem@davemloft.net>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	 Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	 James Clark <james.clark@linaro.org>,
	linux-perf-users@vger.kernel.org, sparclinux@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] perf: user stack dump on sparc64 needs an arch hook
Date: Tue, 22 Sep 2026 22:02:26 +0200	[thread overview]
Message-ID: <a0bee581f87dba8e40ea0055ef8c6a5cfed72ec5.camel@itx.no> (raw)
In-Reply-To: <CA+=Fv5RnsBXnxb2JHfZ2kXkYB7fz3KLS3+oHtx==z9W93WRANA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2245 bytes --]

Hi Magnus, thanks for the testing and feedback.

Almost done with a v2.

It has some minor changes based on the AI bot feedback, and my comments
to you below.


On Tue, 2026-09-22 at 19:04 +0200, Magnus Lindholm wrote:
> 
> Very nice series, thanks for working on this!
> 
> I built and booted the series on a sparc64 box and haven't
> noticed any regressions so far.
> 
> I also smoke-tested the new interfaces from 64-bit userspace with a
> small standalone C program using perf_event_open() and software
> cpu-clock events. The register-only, stack-only, and combined
> register/stack tests all passed. The test does not use tools/perf or
> request PERF_SAMPLE_CALLCHAIN. I haven't tested end-to-end DWARF
> unwinding yet.
> 
> I see that you plan to post the userspace changes once the hook is
> settled. Could you include the tools/perf support in the next
> revision,
> or post it as a follow-up or linked companion series? Having that
> available, along with a link to the matching elfutils changes, would
> make testing easier and let us exercise the intended DWARF unwinding
> use case directly.
Yes, I originally planned to post tools/perf after I got some feedback
on the first patches. Especially since it touches some generic code
that I'm not too familiar with, and I half expect that I have to
rewrite some of it based on maintainer feedback :-)

But since its "just" a RFC patch at this point, I guess I can post the
full series to allow end-to-end testing. 

I have mainly focused on the first patches, and the rest was done a bit
faster as a means to validate the "core" changes. It works (TM). I'm
looking through it now, but I probably make a second thorough review of
the entire final series, once the I know what changes I need to make.

I will publish and link to the elfutils changes as well.
> 
> Also, could you update the sparc entries from TODO to ok in:
> 
>   Documentation/features/perf/perf-regs/arch-support.txt
>   Documentation/features/perf/perf-stackdump/arch-support.txt
> 
> Those updates would fit naturally in patch 2 alongside the
> HAVE_PERF_REGS and HAVE_PERF_USER_STACK_DUMP selections.
Yes, agree.



-- 
Best regards
Stian Halseth
​

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-09-22 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 13:56 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 13:56 ` [RFC PATCH 2/2] sparc64: Support PERF_SAMPLE_REGS_USER and PERF_SAMPLE_STACK_USER Stian Halseth
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 [this message]

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=a0bee581f87dba8e40ea0055ef8c6a5cfed72ec5.camel@itx.no \
    --to=stian@itx.no \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andreas@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linmag7@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sparclinux@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®