Searched refs:kfunc (Results 1 – 9 of 9) sorted by relevance
| /linux/tools/testing/selftests/bpf/verifier/ |
| H A D | sleepable.c | 9 .kfunc = "bpf_fentry_test1",
22 .kfunc = "bpf_fentry_test1",
35 .kfunc = "bpf_fentry_test1",
48 .kfunc = "task",
60 .kfunc = "bpf",
73 .kfunc = "bpf_fentry_test1",
86 .kfunc = "sched_switch",
|
| H A D | atomic_fetch_add.c | 103 .kfunc = "bpf_fentry_test7",
|
| /linux/Documentation/bpf/ |
| H A D | kfuncs.rst | 18 2. Defining a kfunc
24 valid context. To enforce this, visibility of a kfunc can be per program type.
29 2.1 Creating a wrapper kfunc
32 When defining a wrapper kfunc, the wrapper function should have extern linkage.
33 This prevents the compiler from optimizing away dead code, as this wrapper kfunc
35 prototype in a header for the wrapper kfunc.
49 A wrapper kfunc is often needed when we need to annotate parameters of the
50 kfunc. Otherwise one may directly make the kfunc visible to the BPF program by
53 2.2 Annotating kfunc parameters
59 kfunc with a __tag, where tag may be one of the supported annotations.
[all …]
|
| H A D | cpumasks.rst | 186 As we'll see below, any kfunc that mutates its cpumask argument will take a
381 could easily be encapsulated in a new kfunc if and when required. If you'd like
383 do add a new cpumask kfunc, please document it here, and add any relevant
|
| H A D | bpf_licensing.rst | 85 directly via unstable interface also known as "kfunc".
|
| H A D | graph_ds_impl.rst | 166 kfunc, or via ``bpf_obj_drop``, which ``free``'s the pointee
257 ``bpf_rbtree_remove``. The logic here being that any graph API kfunc which:
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | test_verifier.c | 84 const char *kfunc; member
164 const char *kfunc; member
976 while (fixup_kfunc_btf_id->kfunc) { in fixup_prog_kfuncs()
983 fixup_kfunc_btf_id->kfunc, in fixup_prog_kfuncs()
993 fixup_kfunc_btf_id->kfunc, in fixup_prog_kfuncs()
1577 prog_type == BPF_PROG_TYPE_LSM) && test->kfunc) { in do_test_single()
1580 attach_btf_id = libbpf_find_vmlinux_btf_id(test->kfunc, in do_test_single()
1584 test->kfunc); in do_test_single()
|
| /linux/Documentation/networking/ |
| H A D | xdp-rx-metadata.rst | 39 to indicate the device driver have not implemented this kfunc.
119 It is possible to query which kfunc the particular netdev implements via
|
| /linux/Documentation/hid/ |
| H A D | hid-bpf.rst | 379 /* HID-BPF kfunc API definitions */
460 /* some more HID-BPF kfunc API definitions */
|