From: Tao Chen <chen.dylane@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
haoluo@google.com, jolsa@kernel.org, qmo@kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 1/2] libbpf: Add libbpf_probe_bpf_kfunc API
Date: Fri, 24 Jan 2025 11:25:42 +0800 [thread overview]
Message-ID: <26e2e47f-4c95-4874-969f-c497aadbb5f0@gmail.com> (raw)
In-Reply-To: <8d286a6b2a5f481e1eb23466c199a1b05ec81a88.camel@gmail.com>
在 2025/1/24 09:34, Eduard Zingerman 写道:
> On Fri, 2025-01-24 at 01:05 +0800, Tao Chen wrote:
>
> [...]
>
>> +int libbpf_probe_bpf_kfunc(enum bpf_prog_type prog_type, int kfunc_id,
>> + __s16 off, const void *opts)
> ^^^
> Nit: maybe name this btf_fd?
Hi Eduard, thank you for your guidance, ack, i will send it in v3.
>
>> +{
>
> In v2 function looks identical to libbpf_probe_bpf_helper,
> do we want to copy-paste it or introduce a utility:
>
> static int probe_insn(enum bpf_prog_type prog_type, struct bpf_insn insn,
> const char **accepted_msgs)
>
> And call it from both libbpf_probe_bpf_{helper,kfunc}?
Yes, it seems much more concise. I will send it in v3. Thanks.
>
>> + struct bpf_insn insns[] = {
>> + BPF_EXIT_INSN(),
>> + BPF_EXIT_INSN(),
>> + };
>> + const size_t insn_cnt = ARRAY_SIZE(insns);
>> + int err;
>> + char buf[4096];
>> +
>> + if (opts)
>> + return libbpf_err(-EINVAL);
>> +
>> + /* Same logic as probe_bpf_helper check */
>> + switch (prog_type) {
>> + case BPF_PROG_TYPE_TRACING:
>> + case BPF_PROG_TYPE_EXT:
>> + case BPF_PROG_TYPE_LSM:
>> + case BPF_PROG_TYPE_STRUCT_OPS:
>> + return -EOPNOTSUPP;
>> + default:
>> + break;
>> + }
>> +
>> + insns[0].code = BPF_JMP | BPF_CALL;
>> + insns[0].src_reg = BPF_PSEUDO_KFUNC_CALL;
>> + insns[0].imm = kfunc_id;
>> + insns[0].off = off;
>> +
>> + buf[0] = '\0';
>> + err = probe_prog_load(prog_type, insns, insn_cnt, buf, sizeof(buf));
>> + if (err < 0)
>> + return libbpf_err(err);
>> +
>> + /* If BPF verifier recognizes BPF kfunc but it's not supported for
>> + * given BPF program type, it will emit "calling kernel function
>> + * bpf_cpumask_create is not allowed", if the kfunc id is invalid,
>> + * it will emit "kernel btf_id 4294967295 is not a function"
>> + */
>> + if (err == 0 && (strstr(buf, "not allowed") || strstr(buf, "not a function")))
>> + return 0;
>> +
>> + return 1; /* assume supported */
>> +}
>> +
>> int libbpf_probe_bpf_helper(enum bpf_prog_type prog_type, enum bpf_func_id helper_id,
>> const void *opts)
>> {
>
>
--
Best Regards
Dylane Chen
next prev parent reply other threads:[~2025-01-24 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 17:05 [PATCH bpf-next v2 0/2] Add prog_kfunc feature probe Tao Chen
2025-01-23 17:05 ` [PATCH bpf-next v2 1/2] libbpf: Add libbpf_probe_bpf_kfunc API Tao Chen
2025-01-24 1:34 ` Eduard Zingerman
2025-01-24 3:25 ` Tao Chen [this message]
2025-01-23 17:05 ` [PATCH bpf-next v2 2/2] selftests/bpf: Add libbpf_probe_bpf_kfunc API selftests Tao Chen
2025-01-24 0:42 ` [PATCH bpf-next v2 0/2] Add prog_kfunc feature probe Eduard Zingerman
2025-01-24 2:49 ` 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=26e2e47f-4c95-4874-969f-c497aadbb5f0@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