From: Amery Hung <ameryhung@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii@kernel.org, daniel@iogearbox.net, tj@kernel.org,
martin.lau@kernel.org, ameryhung@gmail.com, kernel-team@meta.com
Subject: [RFC PATCH v1 bpf-next 0/4] Support associating BPF programs with struct_ops
Date: Fri, 10 Oct 2025 10:49:49 -0700 [thread overview]
Message-ID: <20251010174953.2884682-1-ameryhung@gmail.com> (raw)
This patchset adds a new BPF command BPF_STRUCT_OPS_ASSOCIATE_PROG to
the bpf() syscall to allow associating a BPF program with a struct_ops.
The command is introduced to address a emerging need from struct_ops
users. As the number of subsystems adopting struct_ops grows, more
users are building their struct_ops-based solution with some help from
other BPF programs. For exmample, scx_layer uses a syscall program as
a user space trigger to refresh layers [0]. It also uses tracing program
to infer whether a task is using GPU and needs to be prioritized [1]. In
these use cases, when there are multiple struct_ops instances, the
struct_ops kfuncs called from different BPF programs, whether struct_ops
or not needs to be able to refer to a specific one, which currently is
not possible.
The new BPF command will allow users to explicitly associate a BPF
program with a struct_ops map. The libbpf wrapper can be called after
loading programs and before attaching programs and struct_ops.
Internally, it will set prog->aux->st_ops_assoc to the struct_ops
struct (i.e., kdata). struct_ops kfuncs can then get the associated
struct_ops by adding a "__prog" argument. The value of the speical
argument will be fixed up by the verifier during verification.
The command conceptually associates the implementation of BPF programs
with struct_ops map, not the attachment. A program associated with the
map will take a refcount of it so that st_ops_assoc always points to a
valid struct_ops struct. However, the struct_ops can be in an
uninitialized or unattached state. The struct_ops implementer will be
responsible to maintain and check the state of the associated
struct_ops before accessing it.
We can also consider support associating struct_ops link with BPF
programs, which on one hand make struct_ops implementer's job easier,
but might complicate libbpf workflow and does not apply to legacy
struct_ops attachment.
[0] https://github.com/sched-ext/scx/blob/main/scheds/rust/scx_layered/src/bpf/main.bpf.c#L557
[1] https://github.com/sched-ext/scx/blob/main/scheds/rust/scx_layered/src/bpf/main.bpf.c#L754
Amery Hung (4):
bpf: Allow verifier to fixup kernel module kfuncs
bpf: Support associating BPF program with struct_ops
libbpf: Add bpf_struct_ops_associate_prog() API
selftests/bpf: Test BPF_STRUCT_OPS_ASSOCIATE_PROG command
include/linux/bpf.h | 11 ++
include/uapi/linux/bpf.h | 16 +++
kernel/bpf/bpf_struct_ops.c | 32 ++++++
kernel/bpf/core.c | 6 +
kernel/bpf/syscall.c | 38 +++++++
kernel/bpf/verifier.c | 3 +-
tools/include/uapi/linux/bpf.h | 16 +++
tools/lib/bpf/bpf.c | 18 +++
tools/lib/bpf/bpf.h | 19 ++++
tools/lib/bpf/libbpf.map | 1 +
.../bpf/prog_tests/test_struct_ops_assoc.c | 76 +++++++++++++
.../selftests/bpf/progs/struct_ops_assoc.c | 105 ++++++++++++++++++
.../selftests/bpf/test_kmods/bpf_testmod.c | 17 +++
.../bpf/test_kmods/bpf_testmod_kfunc.h | 1 +
14 files changed, 357 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/test_struct_ops_assoc.c
create mode 100644 tools/testing/selftests/bpf/progs/struct_ops_assoc.c
--
2.47.3
next reply other threads:[~2025-10-10 17:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 17:49 Amery Hung [this message]
2025-10-10 17:49 ` [RFC PATCH v1 bpf-next 1/4] bpf: Allow verifier to fixup kernel module kfuncs Amery Hung
2025-10-14 0:10 ` Andrii Nakryiko
2025-10-16 18:29 ` Amery Hung
2025-10-10 17:49 ` [RFC PATCH v1 bpf-next 2/4] bpf: Support associating BPF program with struct_ops Amery Hung
2025-10-14 0:10 ` Andrii Nakryiko
2025-10-15 22:35 ` Amery Hung
2025-10-16 18:41 ` Andrii Nakryiko
2025-10-10 17:49 ` [RFC PATCH v1 bpf-next 3/4] libbpf: Add bpf_struct_ops_associate_prog() API Amery Hung
2025-10-14 0:10 ` Andrii Nakryiko
2025-10-10 17:49 ` [RFC PATCH v1 bpf-next 4/4] selftests/bpf: Test BPF_STRUCT_OPS_ASSOCIATE_PROG command Amery Hung
2025-10-14 0:10 ` Andrii Nakryiko
2025-10-16 18:32 ` Amery Hung
2025-10-14 0:10 ` [RFC PATCH v1 bpf-next 0/4] Support associating BPF programs with struct_ops Andrii Nakryiko
2025-10-16 18:30 ` Amery Hung
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=20251010174953.2884682-1-ameryhung@gmail.com \
--to=ameryhung@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).