Received-SPF: pass (google.com: domain of linux-kernel+bounces-143694-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Sat, 13 Apr 2024 12:53:38 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
	rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	irogers@google.com, adrian.hunter@intel.com, primiano@google.com,
	aahringo@redhat.com, dcook@linux.microsoft.com,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [RFC PATCH 0/4] perf: Correlating user process data to samples
Message-ID: <20240413105338.GD40213@noisy.programming.kicks-ass.net>
References: <20240412001732.475-1-beaub@linux.microsoft.com>
 <20240412071245.GD30852@noisy.programming.kicks-ass.net>
 <20240412163724.GB467-beaub@linux.microsoft.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20240412163724.GB467-beaub@linux.microsoft.com>

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?