From: Tao Chen <chen.dylane@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, haoluo@google.com, jolsa@kernel.org,
qmo@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 1/3] libbpf: Refactor libbpf_probe_bpf_helper
Date: Sat, 25 Jan 2025 23:05:23 +0800 [thread overview]
Message-ID: <aedece31-5531-4ffe-9967-5906ec971cec@gmail.com> (raw)
In-Reply-To: <CAEf4BzYTGiAedD8zEmw16NQ6JWAtkwDU2rhGLGZjXL0H1iKO+g@mail.gmail.com>
在 2025/1/25 02:44, Andrii Nakryiko 写道:
> On Fri, Jan 24, 2025 at 6:44 AM Tao Chen <chen.dylane@gmail.com> wrote:
>>
>> Extract the common part as probe_func_comm, which will be used in
>> both libbpf_probe_bpf_{helper, kfunc}
>>
>> Signed-off-by: Tao Chen <chen.dylane@gmail.com>
>> ---
>> tools/lib/bpf/libbpf_probes.c | 38 ++++++++++++++++++++++++-----------
>> 1 file changed, 26 insertions(+), 12 deletions(-)
>>
>> diff --git a/tools/lib/bpf/libbpf_probes.c b/tools/lib/bpf/libbpf_probes.c
>> index 9dfbe7750f56..b73345977b4e 100644
>> --- a/tools/lib/bpf/libbpf_probes.c
>> +++ b/tools/lib/bpf/libbpf_probes.c
>> @@ -413,22 +413,20 @@ int libbpf_probe_bpf_map_type(enum bpf_map_type map_type, const void *opts)
>> return libbpf_err(ret);
>> }
>>
>> -int libbpf_probe_bpf_helper(enum bpf_prog_type prog_type, enum bpf_func_id helper_id,
>> - const void *opts)
>> +static int probe_func_comm(enum bpf_prog_type prog_type, struct bpf_insn insn,
>> + char *accepted_msgs, size_t msgs_size)
>> {
>> struct bpf_insn insns[] = {
>> - BPF_EMIT_CALL((__u32)helper_id),
>> + BPF_EXIT_INSN(),
>> BPF_EXIT_INSN(),
>> };
>> const size_t insn_cnt = ARRAY_SIZE(insns);
>> - char buf[4096];
>> - int ret;
>> + int err;
>>
>> - if (opts)
>> - return libbpf_err(-EINVAL);
>> + insns[0] = insn;
>>
>> /* we can't successfully load all prog types to check for BPF helper
>> - * support, so bail out with -EOPNOTSUPP error
>> + * and kfunc support, so bail out with -EOPNOTSUPP error
>> */
>> switch (prog_type) {
>> case BPF_PROG_TYPE_TRACING:
>
> there isn't much logic that you will extract here besides this check
> whether program type can even be successfully loaded, so I wouldn't
> extract probe_func_comm(), but rather extract just the check:
>
> static bool can_probe_prog_type(enum bpf_prog_type prog_type)
> {
> /* we can't successfully load all prog types to check for BPF
> helper/kfunc
> * support, so check this early and bail
> */
> switch (prog_type) {
> ...: return false
> default:
> return true;
> }
>
>
> And just check that can_probe_prog_type() inside
> libbpf_probe_bpf_helper and libbpf_probe_bpf_kfunc
>
> pw-bot: cr
>
Hi Andrii,
Thank you for your review, jiri also suggested putting the insn part
back into libbpf_bpf_probe_{helper, kfunc}, so I'll make the
modifications as you suggested in v4.
>> @@ -440,10 +438,26 @@ int libbpf_probe_bpf_helper(enum bpf_prog_type prog_type, enum bpf_func_id helpe
>> break;
>> }
>>
>> - buf[0] = '\0';
>> - ret = probe_prog_load(prog_type, insns, insn_cnt, buf, sizeof(buf));
>> - if (ret < 0)
>> - return libbpf_err(ret);
>> + accepted_msgs[0] = '\0';
>> + err = probe_prog_load(prog_type, insns, insn_cnt, accepted_msgs, msgs_size);
>> + if (err < 0)
>> + return libbpf_err(err);
>> +
>> + return 0;
>> +}
>> +
>> +int libbpf_probe_bpf_helper(enum bpf_prog_type prog_type, enum bpf_func_id helper_id,
>> + const void *opts)
>> +{
>> + char buf[4096];
>> + int ret;
>> +
>> + if (opts)
>> + return libbpf_err(-EINVAL);
>> +
>> + ret = probe_func_comm(prog_type, BPF_EMIT_CALL((__u32)helper_id), buf, sizeof(buf));
>> + if (ret)
>> + return ret;
>>
>> /* If BPF verifier doesn't recognize BPF helper ID (enum bpf_func_id)
>> * at all, it will emit something like "invalid func unknown#181".
>> --
>> 2.43.0
>>
--
Best Regards
Dylane Chen
next prev parent reply other threads:[~2025-01-25 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 14:44 [PATCH bpf-next v3 0/3] Add prog_kfunc feature probe Tao Chen
2025-01-24 14:44 ` [PATCH bpf-next v3 1/3] libbpf: Refactor libbpf_probe_bpf_helper Tao Chen
2025-01-24 16:26 ` Jiri Olsa
2025-01-25 14:52 ` Tao Chen
2025-01-24 18:44 ` Andrii Nakryiko
2025-01-25 15:05 ` Tao Chen [this message]
2025-01-24 14:44 ` [PATCH bpf-next v3 2/3] libbpf: Add libbpf_probe_bpf_kfunc API Tao Chen
2025-01-24 16:27 ` Jiri Olsa
2025-01-25 14:54 ` Tao Chen
2025-01-24 18:46 ` Andrii Nakryiko
2025-01-24 14:44 ` [PATCH bpf-next v3 3/3] selftests/bpf: Add libbpf_probe_bpf_kfunc API selftests Tao Chen
2025-01-24 16:27 ` Jiri Olsa
2025-01-25 14:56 ` Tao Chen
2025-01-24 18:48 ` Andrii Nakryiko
2025-01-25 15:07 ` 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=aedece31-5531-4ffe-9967-5906ec971cec@gmail.com \
--to=chen.dylane@gmail.com \
--cc=andrii.nakryiko@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