Home
last modified time | relevance | path

Searched refs:kfuncs (Results 1 – 10 of 10) sorted by relevance

/linux-6.15/Documentation/bpf/
H A Dfs_kfuncs.rst6 BPF filesystem kfuncs
10 BPF kfuncs can be used to get these data.
16 To avoid recursions, these kfuncs follow the following rules:
18 1. These kfuncs are only permitted from BPF LSM function.
19 2. These kfuncs should not call into other LSM hooks, i.e. security_*(). For
H A Dcpumasks.rst6 BPF cpumask kfuncs
18 BPF provides programs with a set of :ref:`kfuncs-header-label` that can be
142 * be passed to kfuncs using RCU protection.
190 3. cpumask kfuncs
195 kfuncs for mutating and querying cpumasks.
200 Some cpumask kfuncs are "read-only" in that they don't mutate any of their
216 These kfuncs are pretty straightforward, and can be used, for example, as
280 kfuncs shown in this example will be covered in more detail below.
350 In addition to the above kfuncs, there is also a set of read-only kfuncs that
366 Some example usages of these querying kfuncs were shown above. We will not
[all …]
H A Dkfuncs.rst6 BPF Kernel Functions (kfuncs)
173 2.4 Annotating kfuncs
178 flags on a set of kfuncs as follows::
298 The KF_SLEEPABLE flag is used for kfuncs that may sleep. Such kfuncs can only
343 2.5 Registering the kfuncs
461 use kfuncs.
502 4. Core kfuncs
507 Those kfuncs are documented here.
509 4.1 struct task_struct * kfuncs
622 4.2 struct cgroup * kfuncs
[all …]
H A Dindex.rst22 kfuncs
H A Dbpf_design_QA.rst206 New BPF functionality is generally added through the use of kfuncs instead of
239 kfuncs. The set of available functions is defined for every program type.
265 A: Yes, through kfuncs and kptrs
269 by exporting kfuncs (which may return pointers to module-internal data
349 for special fields inside them is exposed through kfuncs, and thus has the same
350 lifecycle expectations as the kfuncs themselves. See
H A Dgraph_ds_impl.rst31 no longer relevant. With the introduction of kfuncs, kptrs, and the any-context
48 or map-specific helpers. The new-style graph data structures instead use kfuncs
50 for kfuncs, the API and semantics for these data structures can be evolved in
266 node. So ``remove``-type kfuncs must be considered a non-owning reference
/linux-6.15/tools/testing/selftests/bpf/progs/
H A Dkprobe_multi_session.c28 const void *kfuncs[] = { in session_check() local
44 for (i = 0; i < ARRAY_SIZE(kfuncs); i++) { in session_check()
45 if (kfuncs[i] == (void *) addr) { in session_check()
/linux-6.15/Documentation/networking/
H A Dxdp-rx-metadata.rst14 XDP has access to a set of kfuncs to manipulate the metadata in an XDP frame.
16 implement these kfuncs. The set of kfuncs is declared in ``include/net/xdp.h``
19 Currently, the following kfuncs are supported. In the future, as more
31 An XDP program can use these kfuncs to read the metadata into stack
37 Not all kfuncs have to be implemented by the device driver; when not
64 of kfuncs to populate it. The userspace ``XSK`` consumer computes
113 Adding programs that access metadata kfuncs to the ``BPF_MAP_TYPE_PROG_ARRAY``
/linux-6.15/tools/bpf/bpftool/
H A Dbtf.c517 struct ptr_array kfuncs = {}; in dump_btf_kfuncs() local
540 err = ptr_array_push(ft, &kfuncs); in dump_btf_kfuncs()
553 qsort_r(kfuncs.elems, kfuncs.cnt, sizeof(*kfuncs.elems), cmp_kfuncs, (void *)btf); in dump_btf_kfuncs()
554 for (i = 0; i < kfuncs.cnt; i++) { in dump_btf_kfuncs()
555 const struct btf_type *t = kfuncs.elems[i]; in dump_btf_kfuncs()
579 ptr_array_free(&kfuncs); in dump_btf_kfuncs()
/linux-6.15/Documentation/scheduler/
H A Dsched-ext.rst355 ``include/linux/sched/ext.h``, as well as the ``scx_bpf_`` kfuncs defined in