On Wed, Nov 06, 2024 at 11:46:39AM +0100, Peter Zijlstra wrote: > On Tue, Nov 05, 2024 at 06:11:07PM -0800, Andrii Nakryiko wrote: > > On Wed, Oct 30, 2024 at 2:42 AM Jiri Olsa <olsajiri@xxxxxxxxx> wrote: > > > > > > On Wed, Oct 16, 2024 at 12:35:21PM -0700, Andrii Nakryiko wrote: > > > > > > SNIP > > > > > > > - 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. > > > > > > > > > Hi Ingo, > > > there's uprobe session support change that already landed in tip tree, > > > but we have bpf related changes that need to go in through bpf-next tree > > > > > > could you please create the stable tag that we could pull to bpf-next/master > > > and apply the rest of the uprobe session changes in there? > > > > Ping. We (BPF) are blocked on this, we can't apply Jiri's uprobe > > session series ([0]), until we merge two of his patches that landed > > into perf/core. Can we please get a stable tag which we can use to > > pull perf/core's patches into bpf-next/master? > > The whole tip/perf/core should be stable, but let me try and figure out > how git tags work.. might as well read a man-page today. I might have managed to create a perf-core-for-bpf-next tag, but I'm not sure I know enough about git to even test it. Let me know..
