From: Jiri Olsa <olsajiri@gmail.com>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jonathan Corbet <corbet@lwn.net>,
bpf@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH bpf-next v1] docs/bpf: Add missing BPF k/uprobe program types to docs
Date: Wed, 29 Oct 2025 12:13:59 +0100 [thread overview]
Message-ID: <aQH293IIz8hvobH7@krava> (raw)
In-Reply-To: <20251028182818.78640-1-donald.hunter@gmail.com>
On Tue, Oct 28, 2025 at 06:28:18PM +0000, Donald Hunter wrote:
> Update the table of program types in the libbpf docs with the missing
> k/uprobe multi and session program types.
>
> Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
> ---
> Documentation/bpf/libbpf/program_types.rst | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/bpf/libbpf/program_types.rst b/Documentation/bpf/libbpf/program_types.rst
> index 218b020a2f81..5e7a202dce5e 100644
> --- a/Documentation/bpf/libbpf/program_types.rst
> +++ b/Documentation/bpf/libbpf/program_types.rst
> @@ -100,10 +100,26 @@ described in more detail in the footnotes.
> | | | ``uretprobe.s+`` [#uprobe]_ | Yes |
> + + +----------------------------------+-----------+
> | | | ``usdt+`` [#usdt]_ | |
> ++ + +----------------------------------+-----------+
> +| | | ``usdt.s+`` [#usdt]_ | Yes |
> + +----------------------------------------+----------------------------------+-----------+
> | | ``BPF_TRACE_KPROBE_MULTI`` | ``kprobe.multi+`` [#kpmulti]_ | |
> + + +----------------------------------+-----------+
> | | | ``kretprobe.multi+`` [#kpmulti]_ | |
> ++ + +----------------------------------+-----------+
> +| | | ``kprobe.session+`` [#kpmulti]_ | |
hi,
uprobe/kprobe session have BPF_TRACE_UPROBE_SESSION/BPF_TRACE_KPROBE_SESSION
attach type respectively
thanks,
jirka
> ++ + +----------------------------------+-----------+
> +| | | ``uprobe.multi+`` [#upmul]_ | |
> ++ + +----------------------------------+-----------+
> +| | | ``uprobe.multi.s+`` [#upmul]_ | Yes |
> ++ + +----------------------------------+-----------+
> +| | | ``uretprobe.multi+`` [#upmul]_ | |
> ++ + +----------------------------------+-----------+
> +| | | ``uretprobe.multi.s+`` [#upmul]_ | Yes |
> ++ + +----------------------------------+-----------+
> +| | | ``uprobe.session+`` [#upmul]_ | |
> ++ + +----------------------------------+-----------+
> +| | | ``uprobe.session.s+`` [#upmul]_ | Yes |
> +-------------------------------------------+----------------------------------------+----------------------------------+-----------+
> | ``BPF_PROG_TYPE_LIRC_MODE2`` | ``BPF_LIRC_MODE2`` | ``lirc_mode2`` | |
> +-------------------------------------------+----------------------------------------+----------------------------------+-----------+
> @@ -219,6 +235,8 @@ described in more detail in the footnotes.
> non-negative integer.
> .. [#ksyscall] The ``ksyscall`` attach format is ``ksyscall/<syscall>``.
> .. [#uprobe] The ``uprobe`` attach format is ``uprobe[.s]/<path>:<function>[+<offset>]``.
> +.. [#upmul] The ``uprobe.multi`` attach format is ``uprobe.multi[.s]/<path>:<function-pattern>``
> + where ``function-pattern`` supports ``*`` and ``?`` wildcards.
> .. [#usdt] The ``usdt`` attach format is ``usdt/<path>:<provider>:<name>``.
> .. [#kpmulti] The ``kprobe.multi`` attach format is ``kprobe.multi/<pattern>`` where ``pattern``
> supports ``*`` and ``?`` wildcards. Valid characters for pattern are
> --
> 2.51.1
>
prev parent reply other threads:[~2025-10-29 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 18:28 [PATCH bpf-next v1] docs/bpf: Add missing BPF k/uprobe program types to docs Donald Hunter
2025-10-29 11:13 ` Jiri Olsa [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=aQH293IIz8hvobH7@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=donald.hunter@gmail.com \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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