public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: oleg@redhat.com, peterz@infradead.org, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, bpf@vger.kernel.org,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	john.fastabend@gmail.com, kpsingh@chromium.org, sdf@fomichev.me,
	haoluo@google.com, rostedt@goodmis.org, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCHv4 00/14] uprobe, bpf: Add session support
Date: Mon, 23 Sep 2024 08:34:38 +0000	[thread overview]
Message-ID: <172708047825.3261420.5126267811201364070.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240917085024.765883-1-jolsa@kernel.org>

Hello:

This series was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Tue, 17 Sep 2024 10:50:10 +0200 you wrote:
> hi,
> this patchset is adding support for session uprobe attachment and
> using it through bpf link for bpf programs.
> 
> The session means that the uprobe consumer is executed on entry
> and return of probed function with additional control:
>   - entry callback can control execution of the return callback
>   - entry and return callbacks can share data/cookie
> 
> [...]

Here is the summary with links:
  - [PATCHv4,01/14] uprobe: Add data pointer to consumer handlers
    (no matching commit)
  - [PATCHv4,02/14] uprobe: Add support for session consumer
    (no matching commit)
  - [PATCHv4,03/14] bpf: Add support for uprobe multi session attach
    (no matching commit)
  - [PATCHv4,04/14] bpf: Add support for uprobe multi session context
    (no matching commit)
  - [PATCHv4,05/14] bpf: Allow return values 0 and 1 for uprobe/kprobe session
    (no matching commit)
  - [PATCHv4,06/14] libbpf: Fix uretprobe.multi.s programs auto attachment
    https://git.kernel.org/bpf/bpf/c/8c8b47597403
  - [PATCHv4,07/14] libbpf: Add support for uprobe multi session attach
    (no matching commit)
  - [PATCHv4,08/14] selftests/bpf: Add uprobe session test
    (no matching commit)
  - [PATCHv4,09/14] selftests/bpf: Add uprobe session cookie test
    (no matching commit)
  - [PATCHv4,10/14] selftests/bpf: Add uprobe session recursive test
    (no matching commit)
  - [PATCHv4,11/14] selftests/bpf: Add uprobe session verifier test for return value
    (no matching commit)
  - [PATCHv4,12/14] selftests/bpf: Add kprobe session verifier test for return value
    (no matching commit)
  - [PATCHv4,13/14] selftests/bpf: Add uprobe session single consumer test
    (no matching commit)
  - [PATCHv4,14/14] selftests/bpf: Add consumers stress test on single uprobe
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-09-23  8:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  8:50 [PATCHv4 00/14] uprobe, bpf: Add session support Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 01/14] uprobe: Add data pointer to consumer handlers Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 02/14] uprobe: Add support for session consumer Jiri Olsa
2024-09-17 12:03   ` Oleg Nesterov
2024-09-17 12:51     ` Jiri Olsa
2024-09-22 15:27       ` Oleg Nesterov
2024-09-23  8:05         ` Jiri Olsa
2024-09-23 10:05           ` Oleg Nesterov
2024-09-23 11:02             ` Jiri Olsa
2024-09-23 12:13               ` Oleg Nesterov
2024-09-17 12:22   ` Oleg Nesterov
2024-09-17  8:50 ` [PATCHv4 03/14] bpf: Add support for uprobe multi session attach Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 04/14] bpf: Add support for uprobe multi session context Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 05/14] bpf: Allow return values 0 and 1 for uprobe/kprobe session Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 06/14] libbpf: Fix uretprobe.multi.s programs auto attachment Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 07/14] libbpf: Add support for uprobe multi session attach Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 08/14] selftests/bpf: Add uprobe session test Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 09/14] selftests/bpf: Add uprobe session cookie test Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 10/14] selftests/bpf: Add uprobe session recursive test Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 11/14] selftests/bpf: Add uprobe session verifier test for return value Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 12/14] selftests/bpf: Add kprobe " Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 13/14] selftests/bpf: Add uprobe session single consumer test Jiri Olsa
2024-09-17  8:50 ` [PATCHv4 14/14] selftests/bpf: Add consumers stress test on single uprobe Jiri Olsa
2024-09-23  8:34 ` patchwork-bot+netdevbpf [this message]

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=172708047825.3261420.5126267811201364070.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sdf@fomichev.me \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox