From: Stian Halseth <stian@itx.no>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Andreas Larsson <andreas@gaisler.com>,
"David S. Miller" <davem@davemloft.net>,
Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Magnus Lindholm <linmag7@gmail.com>,
linux-perf-users@vger.kernel.org, sparclinux@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 0/3] perf: sparc64 user regs and stack dump, with arch hooks
Date: Fri, 25 Sep 2026 09:33:33 +0200 [thread overview]
Message-ID: <41a208e59a2c3dfc824bd93366034f89ea8b8ed3.camel@itx.no> (raw)
In-Reply-To: <arVZtcrJRRxI6jYd@x2>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Hi Arnaldo,
On Thu, 2026-09-24 at 19:11 +0200, Arnaldo Carvalho de Melo wrote:
> On Thu, Sep 24, 2026 at 07:09:58PM +0200, Arnaldo Carvalho de Melo
> wrote:
> > On Wed, Sep 23, 2026 at 02:16:49PM -0700, Ian Rogers wrote:
> > > On Wed, Sep 23, 2026 at 1:57 PM Stian Halseth <stian@itx.no>
> > > wrote:
> > > I think we have everything we need but the kernel changes are
> > > really
> > > up to Peter and Ingo, and the tool changes are up to Arnaldo and
> > > Namhyung.
>
> > Exactly, as soon as the kernel changes land in a path to upstream,
> > I can
> > do the same for the tooling bits.
>
> Once that happens, please resubmit just the tools patches without an
> RFC
> in the subject line.
Will do, thanks!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-25 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 9:04 Stian Halseth
2026-09-23 9:04 ` [RFC PATCH v3 1/3] perf/core: Let an arch prepare and locate the user stack dump Stian Halseth
2026-09-23 9:04 ` [RFC PATCH v3 2/3] sparc64: Support PERF_SAMPLE_REGS_USER and PERF_SAMPLE_STACK_USER Stian Halseth
2026-09-23 9:04 ` [RFC PATCH v3 3/3] perf tools: Support sparc user register samples and dwarf unwinding Stian Halseth
2026-09-23 20:38 ` [RFC PATCH v3 0/3] perf: sparc64 user regs and stack dump, with arch hooks Ian Rogers
2026-09-23 20:56 ` Stian Halseth
2026-09-23 21:16 ` Ian Rogers
2026-09-24 17:09 ` Arnaldo Carvalho de Melo
2026-09-24 17:11 ` Arnaldo Carvalho de Melo
2026-09-25 7:33 ` Stian Halseth [this message]
2026-09-23 23:10 ` Magnus Lindholm
2026-09-24 8:20 ` 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=41a208e59a2c3dfc824bd93366034f89ea8b8ed3.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=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linmag7@gmail.com \
--cc=linux-doc@vger.kernel.org \
--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=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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®