From: JP Kobryn <inwardvessel@gmail.com>
To: andrii@kernel.org, ast@kernel.org, eddyz87@gmail.com,
bpf@vger.kernel.org
Subject: [PATCH bpf-next v3 0/2] allow kfuncs in tracepoint and perf event
Date: Thu, 5 Sep 2024 15:38:10 -0700 [thread overview]
Message-ID: <20240905223812.141857-1-inwardvessel@gmail.com> (raw)
It is possible to call a cpumask kfunc within a raw tp_btf program but not
possible within tracepoint or perf event programs. Currently, the verifier
receives -EACCESS from fetch_kfunc_meta() as a result of not finding any
kfunc hook associated with these program types.
This patch series associates tracepoint and perf event program types with
the tracing hook and includes test coverage.
Pre-submission CI run: https://github.com/kernel-patches/bpf/pull/7674
v3:
- map tracepoint and perf event progs to tracing kfunc hook
- expand existing verifier tests for kfuncs
- remove explicit registrations from v2
- no longer including kprobes
v2:
- create new kfunc hooks for tracepoint and perf event
- map tracepoint, and perf event prog types to kfunc hooks
- register cpumask kfuncs with prog types in focus
- expand existing verifier tests for cpumask kfuncs
v1:
- map tracepoint type progs to tracing kfunc hook
- new selftests for calling cpumask kfuncs in tracepoint prog
---
JP Kobryn (2):
bpf: allow kfuncs within tracepoint and perf event programs
bpf/selftests: coverage for new program types using cpumask kfuncs
kernel/bpf/btf.c | 2 ++
.../bpf/progs/verifier_kfunc_prog_types.c | 16 ++++++++++++++++
2 files changed, 18 insertions(+)
--
2.46.0
next reply other threads:[~2024-09-05 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 22:38 JP Kobryn [this message]
2024-09-05 22:38 ` [PATCH bpf-next v3 1/2] bpf: allow kfuncs within tracepoint and perf event programs JP Kobryn
2024-09-05 22:38 ` [PATCH bpf-next v3 2/2] bpf/selftests: coverage for tp and perf event progs using kfuncs JP Kobryn
2024-09-06 0:10 ` [PATCH bpf-next v3 0/2] allow kfuncs in tracepoint and perf event patchwork-bot+netdevbpf
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=20240905223812.141857-1-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