public inbox for bpf@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: [PATCHv9 bpf-next 00/13] bpf: Add uprobe session support
Date: Fri, 08 Nov 2024 18:40:32 +0000	[thread overview]
Message-ID: <173109123276.2726733.16157399408495124649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241108134544.480660-1-jolsa@kernel.org>

Hello:

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

On Fri,  8 Nov 2024 14:45:31 +0100 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:
  - [PATCHv9,bpf-next,01/13] bpf: Allow return values 0 and 1 for kprobe session
    https://git.kernel.org/bpf/bpf-next/c/1c9b65d7b569
  - [PATCHv9,bpf-next,02/13] bpf: Force uprobe bpf program to always return 0
    https://git.kernel.org/bpf/bpf-next/c/fb9618060bb7
  - [PATCHv9,bpf-next,03/13] bpf: Add support for uprobe multi session attach
    https://git.kernel.org/bpf/bpf-next/c/4c2c20b698ce
  - [PATCHv9,bpf-next,04/13] bpf: Add support for uprobe multi session context
    https://git.kernel.org/bpf/bpf-next/c/362ced90a9b9
  - [PATCHv9,bpf-next,05/13] libbpf: Add support for uprobe multi session attach
    https://git.kernel.org/bpf/bpf-next/c/894d0bd715f8
  - [PATCHv9,bpf-next,06/13] selftests/bpf: Add uprobe session test
    https://git.kernel.org/bpf/bpf-next/c/1932f3ffe604
  - [PATCHv9,bpf-next,07/13] selftests/bpf: Add uprobe session cookie test
    https://git.kernel.org/bpf/bpf-next/c/dce1b3b721b8
  - [PATCHv9,bpf-next,08/13] selftests/bpf: Add uprobe session recursive test
    https://git.kernel.org/bpf/bpf-next/c/9236020b0896
  - [PATCHv9,bpf-next,09/13] selftests/bpf: Add uprobe session verifier test for return value
    https://git.kernel.org/bpf/bpf-next/c/a773e1d169db
  - [PATCHv9,bpf-next,10/13] selftests/bpf: Add kprobe session verifier test for return value
    https://git.kernel.org/bpf/bpf-next/c/7dd198ccbe43
  - [PATCHv9,bpf-next,11/13] selftests/bpf: Add uprobe session single consumer test
    https://git.kernel.org/bpf/bpf-next/c/beab56332941
  - [PATCHv9,bpf-next,12/13] selftests/bpf: Add uprobe sessions to consumer test
    https://git.kernel.org/bpf/bpf-next/c/f343d91be2cb
  - [PATCHv9,bpf-next,13/13] selftests/bpf: Add threads to consumer test
    https://git.kernel.org/bpf/bpf-next/c/90aac4610851

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-11-08 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 13:45 [PATCHv9 bpf-next 00/13] bpf: Add uprobe session support Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 01/13] bpf: Allow return values 0 and 1 for kprobe session Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 02/13] bpf: Force uprobe bpf program to always return 0 Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 03/13] bpf: Add support for uprobe multi session attach Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 04/13] bpf: Add support for uprobe multi session context Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 05/13] libbpf: Add support for uprobe multi session attach Jiri Olsa
2024-11-15  3:59   ` Andrii Nakryiko
2024-11-08 13:45 ` [PATCHv9 bpf-next 06/13] selftests/bpf: Add uprobe session test Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 07/13] selftests/bpf: Add uprobe session cookie test Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 08/13] selftests/bpf: Add uprobe session recursive test Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 09/13] selftests/bpf: Add uprobe session verifier test for return value Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 10/13] selftests/bpf: Add kprobe " Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 11/13] selftests/bpf: Add uprobe session single consumer test Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 12/13] selftests/bpf: Add uprobe sessions to " Jiri Olsa
2024-11-08 13:45 ` [PATCHv9 bpf-next 13/13] selftests/bpf: Add threads " Jiri Olsa
2024-11-08 18:40 ` 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=173109123276.2726733.16157399408495124649.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