[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240413105338.GD40213@noisy.programming.kicks-ass.net>
Date: Sat, 13 Apr 2024 12:53:38 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Beau Belgrave <beaub@...ux.microsoft.com>
Cc: mingo@...hat.com, acme@...nel.org, namhyung@...nel.org,
rostedt@...dmis.org, mhiramat@...nel.org,
mathieu.desnoyers@...icios.com, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, mark.rutland@....com,
alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
irogers@...gle.com, adrian.hunter@...el.com, primiano@...gle.com,
aahringo@...hat.com, dcook@...ux.microsoft.com,
Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [RFC PATCH 0/4] perf: Correlating user process data to samples
On Fri, Apr 12, 2024 at 09:37:24AM -0700, Beau Belgrave wrote:
> > Anyway, since we typically run stuff from NMI context, accessing user
> > data is 'interesting'. As such I would really like to make this work
> > depend on the call-graph rework that pushes all the user access bits
> > into return-to-user.
>
> Cool, I assume that's the SFRAME work? Are there pointers to work I
> could look at and think about what a rebase looks like? Or do you have
> someone in mind I should work with for this?
I've been offline for a little while and still need to catch up with
things myself.
Josh was working on that when I dropped off IIRC, I'm not entirely sure
where things are at currently (and there is no way I can ever hope to
process the backlog).
Anybody know where we are with that?
Powered by blists - more mailing lists