[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZxLEoPQXiNT-MCdt@krava>
Date: Fri, 18 Oct 2024 22:27:12 +0200
From: Jiri Olsa <olsajiri@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Andrii Nakryiko <andrii.nakryiko@...il.com>,
Will Deacon <will@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Mark Rutland <mark.rutland@....com>,
Linux trace kernel <linux-trace-kernel@...r.kernel.org>,
bpf <bpf@...r.kernel.org>, Oleg Nesterov <oleg@...hat.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Liao Chang <liaochang1@...wei.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
"linux-perf-use." <linux-perf-users@...r.kernel.org>,
Kernel Team <kernel-team@...a.com>
Subject: Re: The state of uprobes work and logistics
On Fri, Oct 18, 2024 at 09:36:28AM +0200, Peter Zijlstra wrote:
> On Wed, Oct 16, 2024 at 12:35:21PM -0700, Andrii Nakryiko wrote:
>
> > - Jiri Olsa's uprobe "session" support ([5]). This is less
> > performance focused, but important functionality by itself. But I'm
> > calling this out here because the first two patches are pure uprobe
> > internal changes, and I believe they should go into tip/perf/core to
> > avoid conflicts with the rest of pending uprobe changes.
> >
> > Peter, do you mind applying those two and creating a stable tag for
> > bpf-next to pull? We'll apply the rest of Jiri's series to
> > bpf-next/master.
>
> > [5] https://lore.kernel.org/bpf/20241015091050.3731669-1-jolsa@kernel.org/
>
> I don't actually appear to have these.. Jiri, can you bounce them my
> way or resend?
sorry about that, I split the uprobe perf/core changes and reposted [1]
thanks,
jirka
[1] https://lore.kernel.org/bpf/20241018202252.693462-1-jolsa@kernel.org/T/#ma43c549c4bf684ca1b17fa638aa5e7cbb46893e9
Powered by blists - more mailing lists