From: JP Kobryn <inwardvessel@gmail.com>
To: andrii@kernel.org, ast@kernel.org, eddyz87@gmail.com,
bpf@vger.kernel.org
Subject: [PATCH bpf-next v2 2/3] bpf: register additional prog types with cpumask kfuncs
Date: Mon, 26 Aug 2024 15:48:13 -0700 [thread overview]
Message-ID: <20240826224814.289034-3-inwardvessel@gmail.com> (raw)
In-Reply-To: <20240826224814.289034-1-inwardvessel@gmail.com>
Allow the cpumask family of kfuncs to be called within tracepoint, kprobe,
and perf event programs.
Signed-off-by: JP Kobryn <inwardvessel@gmail.com>
---
kernel/bpf/cpumask.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/bpf/cpumask.c b/kernel/bpf/cpumask.c
index 33c473d676a5..30b0164a2212 100644
--- a/kernel/bpf/cpumask.c
+++ b/kernel/bpf/cpumask.c
@@ -475,6 +475,9 @@ static int __init cpumask_kfunc_init(void)
ret = ret ?: register_btf_kfunc_id_set(BPF_PROG_TYPE_TRACING, &cpumask_kfunc_set);
ret = ret ?: register_btf_kfunc_id_set(BPF_PROG_TYPE_STRUCT_OPS, &cpumask_kfunc_set);
ret = ret ?: register_btf_kfunc_id_set(BPF_PROG_TYPE_SYSCALL, &cpumask_kfunc_set);
+ ret = ret ?: register_btf_kfunc_id_set(BPF_PROG_TYPE_TRACEPOINT, &cpumask_kfunc_set);
+ ret = ret ?: register_btf_kfunc_id_set(BPF_PROG_TYPE_KPROBE, &cpumask_kfunc_set);
+ ret = ret ?: register_btf_kfunc_id_set(BPF_PROG_TYPE_PERF_EVENT, &cpumask_kfunc_set);
return ret ?: register_btf_id_dtor_kfuncs(cpumask_dtors,
ARRAY_SIZE(cpumask_dtors),
THIS_MODULE);
--
2.46.0
next prev parent reply other threads:[~2024-08-26 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 22:48 [PATCH bpf-next v2 0/3] allow cpumask kfuncs in tracepoint, kprobe, perf event JP Kobryn
2024-08-26 22:48 ` [PATCH bpf-next v2 1/3] bpf: new btf kfunc hooks for tracepoint and " JP Kobryn
2024-08-27 21:01 ` Alexei Starovoitov
2024-08-27 22:42 ` Andrii Nakryiko
2024-08-28 19:08 ` JP Kobryn
2024-08-31 2:14 ` Alexei Starovoitov
2024-08-26 22:48 ` JP Kobryn [this message]
2024-08-26 22:48 ` [PATCH bpf-next v2 3/3] bpf/selftests: coverage for new program types using cpumask kfuncs JP Kobryn
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=20240826224814.289034-3-inwardvessel@gmail.com \
--to=inwardvessel@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.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