From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Ingo Molnar <mingo@kernel.org>
Cc: Peter Ziljstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Oleg Nesterov <oleg@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Liao Chang <liaochang1@huawei.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>,
Kernel Team <kernel-team@meta.com>
Subject: Re: The state of uprobes work and logistics
Date: Wed, 30 Oct 2024 10:42:21 +0100 [thread overview]
Message-ID: <ZyH_fWNeL3XYNEH1@krava> (raw)
In-Reply-To: <CAEf4BzarhiBHAQXECJzP5e-z0fbSaTpfQNPaSXwdgErz2f0vUA@mail.gmail.com>
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?
thanks,
jirka
next prev parent reply other threads:[~2024-10-30 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 19:35 The state of uprobes work and logistics Andrii Nakryiko
2024-10-18 7:36 ` Peter Zijlstra
2024-10-18 20:27 ` Jiri Olsa
2024-10-23 17:38 ` Andrii Nakryiko
2024-10-24 17:38 ` Jiri Olsa
2024-10-30 9:42 ` Jiri Olsa [this message]
2024-11-06 2:11 ` Andrii Nakryiko
2024-11-06 10:46 ` Peter Zijlstra
2024-11-06 11:05 ` Peter Zijlstra
2024-11-06 16:15 ` Andrii Nakryiko
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=ZyH_fWNeL3XYNEH1@krava \
--to=olsajiri@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@meta.com \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.