From: Tao Chen <chen.dylane@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, haoluo@google.com, jolsa@kernel.org,
qmo@kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND bpf-next v7 0/4] Add prog_kfunc feature probe
Date: Mon, 17 Feb 2025 13:21:31 +0800 [thread overview]
Message-ID: <2b025df3-144b-4909-a2b4-66356540f71c@gmail.com> (raw)
In-Reply-To: <20250212153912.24116-1-chen.dylane@gmail.com>
在 2025/2/12 23:39, Tao Chen 写道:
> More and more kfunc functions are being added to the kernel.
> Different prog types have different restrictions when using kfunc.
> Therefore, prog_kfunc probe is added to check whether it is supported,
> and the use of this api will be added to bpftool later.
>
> Change list:
> - v6 -> v7:
> - wrap err with libbpf_err
> - comments fix
> - handle btf_fd < 0 as vmlinux
> - patchset Reviewed-by: Jiri Olsa <jolsa@kernel.org>
> - v6
> https://lore.kernel.org/bpf/20250211111859.6029-1-chen.dylane@gmail.com
>
> - v5 -> v6:
> - remove fd_array_cnt
> - test case clean code
> - v5
> https://lore.kernel.org/bpf/20250210055945.27192-1-chen.dylane@gmail.com
>
> - v4 -> v5:
> - use fd_array on stack
> - declare the scope of use of btf_fd
> - v4
> https://lore.kernel.org/bpf/20250206051557.27913-1-chen.dylane@gmail.com/
>
> - v3 -> v4:
> - add fd_array init for kfunc in mod btf
> - add test case for kfunc in mod btf
> - refactor common part as prog load type check for
> libbpf_probe_bpf_{helper,kfunc}
> - v3
> https://lore.kernel.org/bpf/20250124144411.13468-1-chen.dylane@gmail.com
>
> - v2 -> v3:
> - rename parameter off with btf_fd
> - extract the common part for libbpf_probe_bpf_{helper,kfunc}
> - v2
> https://lore.kernel.org/bpf/20250123170555.291896-1-chen.dylane@gmail.com
>
> - v1 -> v2:
> - check unsupported prog type like probe_bpf_helper
> - add off parameter for module btf
> - check verifier info when kfunc id invalid
> - v1
> https://lore.kernel.org/bpf/20250122171359.232791-1-chen.dylane@gmail.com
>
> Tao Chen (4):
> libbpf: Extract prog load type check from libbpf_probe_bpf_helper
> libbpf: Init fd_array when prog probe load
> libbpf: Add libbpf_probe_bpf_kfunc API
> selftests/bpf: Add libbpf_probe_bpf_kfunc API selftests
>
> tools/lib/bpf/libbpf.h | 19 ++-
> tools/lib/bpf/libbpf.map | 1 +
> tools/lib/bpf/libbpf_probes.c | 86 +++++++++++---
> .../selftests/bpf/prog_tests/libbpf_probes.c | 111 ++++++++++++++++++
> 4 files changed, 201 insertions(+), 16 deletions(-)
>
Ping...
Hi Andrii, Eduard,
I've revised the previous suggestions. Please review it again. Thanks.
--
Best Regards
Dylane Chen
next prev parent reply other threads:[~2025-02-17 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 15:39 Tao Chen
2025-02-12 15:39 ` [PATCH bpf-next v7 1/4] libbpf: Extract prog load type check from libbpf_probe_bpf_helper Tao Chen
2025-02-12 15:39 ` [PATCH bpf-next v7 2/4] libbpf: Init fd_array when prog probe load Tao Chen
2025-02-12 15:39 ` [PATCH bpf-next v7 3/4] libbpf: Add libbpf_probe_bpf_kfunc API Tao Chen
2025-02-12 15:39 ` [PATCH bpf-next v7 4/4] selftests/bpf: Add libbpf_probe_bpf_kfunc API selftests Tao Chen
2025-02-17 5:21 ` Tao Chen [this message]
2025-02-18 22:51 ` [PATCH RESEND bpf-next v7 0/4] Add prog_kfunc feature probe Eduard Zingerman
2025-02-20 18:09 ` Tao Chen
2025-02-20 18:43 ` Eduard Zingerman
2025-02-21 10:03 ` Tao Chen
2025-02-21 1:07 ` Andrii Nakryiko
2025-02-21 1:11 ` Eduard Zingerman
2025-02-21 10:03 ` Tao Chen
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=2b025df3-144b-4909-a2b4-66356540f71c@gmail.com \
--to=chen.dylane@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qmo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®