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 1/3] bpf: new btf kfunc hooks for tracepoint and perf event
Date: Mon, 26 Aug 2024 15:48:12 -0700 [thread overview]
Message-ID: <20240826224814.289034-2-inwardvessel@gmail.com> (raw)
In-Reply-To: <20240826224814.289034-1-inwardvessel@gmail.com>
The additional hooks (and prog-to-hook mapping) for tracepoint and perf
event programs allow for registering kfuncs to be used within these
program types.
Signed-off-by: JP Kobryn <inwardvessel@gmail.com>
---
kernel/bpf/btf.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
index 520f49f422fe..4816e309314e 100644
--- a/kernel/bpf/btf.c
+++ b/kernel/bpf/btf.c
@@ -210,6 +210,7 @@ enum btf_kfunc_hook {
BTF_KFUNC_HOOK_TC,
BTF_KFUNC_HOOK_STRUCT_OPS,
BTF_KFUNC_HOOK_TRACING,
+ BTF_KFUNC_HOOK_TRACEPOINT,
BTF_KFUNC_HOOK_SYSCALL,
BTF_KFUNC_HOOK_FMODRET,
BTF_KFUNC_HOOK_CGROUP_SKB,
@@ -219,6 +220,7 @@ enum btf_kfunc_hook {
BTF_KFUNC_HOOK_LWT,
BTF_KFUNC_HOOK_NETFILTER,
BTF_KFUNC_HOOK_KPROBE,
+ BTF_KFUNC_HOOK_PERF_EVENT,
BTF_KFUNC_HOOK_MAX,
};
@@ -8306,6 +8308,8 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)
case BPF_PROG_TYPE_TRACING:
case BPF_PROG_TYPE_LSM:
return BTF_KFUNC_HOOK_TRACING;
+ case BPF_PROG_TYPE_TRACEPOINT:
+ return BTF_KFUNC_HOOK_TRACEPOINT;
case BPF_PROG_TYPE_SYSCALL:
return BTF_KFUNC_HOOK_SYSCALL;
case BPF_PROG_TYPE_CGROUP_SKB:
@@ -8326,6 +8330,8 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)
return BTF_KFUNC_HOOK_NETFILTER;
case BPF_PROG_TYPE_KPROBE:
return BTF_KFUNC_HOOK_KPROBE;
+ case BPF_PROG_TYPE_PERF_EVENT:
+ return BTF_KFUNC_HOOK_PERF_EVENT;
default:
return BTF_KFUNC_HOOK_MAX;
}
--
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 ` JP Kobryn [this message]
2024-08-27 21:01 ` [PATCH bpf-next v2 1/3] bpf: new btf kfunc hooks for tracepoint and " 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 ` [PATCH bpf-next v2 2/3] bpf: register additional prog types with cpumask kfuncs JP Kobryn
2024-08-26 22:48 ` [PATCH bpf-next v2 3/3] bpf/selftests: coverage for new program types using " 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-2-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