Searched refs:programs (Results 1 – 25 of 337) sorted by relevance
12345678910>>...14
| /linux-6.6.21/Documentation/bpf/libbpf/ |
| D | libbpf_overview.rst | 9 heavy lifting of loading, verifying, and attaching BPF programs to various
15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
18 over the interactions between user space and BPF programs.
20 The skeleton file simplifies the process for the user space programs to access
21 global variables and work with BPF programs.
25 BPF programs that can be compiled once and run across different kernel
35 A BPF application consists of one or more BPF programs (either cooperating or
37 variables are shared between all BPF programs, which allows them to cooperate on
38 a common set of data. libbpf provides APIs that user space programs can use to
[all …]
|
| /linux-6.6.21/samples/bpf/ |
| D | tcp_bpf.readme | 2 programs. These programs attach to a cgroupv2. The following commands create
12 (attach) one of the tcp_*_kern.o programs:
19 The tcp_*_kern.o programs use special print functions to print logging
23 cgroupv2 to which the BPF programs are attached (i.e. under bash shell
|
| /linux-6.6.21/tools/bpf/bpftool/Documentation/ |
| D | bpftool-net.rst | 47 For programs attached to a particular cgroup, e.g.,
52 bpf programs, users should consult other tools, e.g., iproute2.
56 and finally netfilter programs. Both xdp programs and tcx/tc programs are
57 ordered based on ifindex number. If multiple bpf programs attached
59 all bpf programs attached to tcx, then tc classes, then all bpf programs
60 attached to non clsact qdiscs, and finally all bpf programs attached
|
| D | bpftool-prog.rst | 69 Show information about loaded programs. If *PROG* is
70 specified show information only about given programs,
71 otherwise list all programs currently loaded on the system.
73 programs which will all be shown.
79 programs (such as the total time spent running the program,
88 programs. On such kernels bpftool will automatically emit this
92 Dump eBPF instructions of the programs from the kernel. By
98 programs which will all be dumped. However, if **file** or
108 If the programs have line_info available, the source line will
135 *OBJ* as *PATH*. **bpftool prog loadall** pins all programs
[all …]
|
| D | bpftool-cgroup.rst | 50 List all programs attached to the cgroup *CGROUP*.
55 If **effective** is specified retrieve effective programs that
61 attached programs. If *CGROUP_ROOT* is not specified,
68 If **effective** is specified retrieve effective programs that
86 Multiple programs are allowed to be attached to a cgroup with
134 Show file names of pinned programs.
|
| D | bpftool-gen.rst | 60 with BPF programs from userspace side. Generated code is
70 programs, skeleton provides a storage for BPF links (**struct
72 requested, supported BPF programs will be automatically
75 programs that can't be automatically attached by libbpf,
80 rely on libbpf support to detach programs and free up
102 specific maps, programs, etc.
121 programs, initializes global data maps. It corresponds to
131 programs of types supported by libbpf for auto-attachment
133 instantiated. For other BPF programs, user can manually
140 Detach and unload BPF programs, free up all the resources
[all …]
|
| D | common_options.rst | 11 programs (**bpftool prog dump jited**) and usage of BPF skeletons
25 load programs.
|
| /linux-6.6.21/Documentation/bpf/ |
| D | bpf_design_QA.rst | 32 A: Because BPF programs are designed to run in the linux kernel
49 Q: Can BPF programs access instruction pointer or return address?
53 Q: Can BPF programs access stack pointer ?
69 BPF programs and programs call kernel helpers with zero overhead,
71 for JITed BPF programs that are indistinguishable from
112 versions will accept all bpf programs that were accepted by
155 workaround would be acceptable. Turned out that programs lose performance
174 programs for 32-bit architectures.
198 A: YES. BPF instructions, arguments to BPF programs, set of helper
200 of ABI. However there is one specific exception to tracing programs
[all …]
|
| D | drgn.rst | 23 `bpf_inspect.py`_ is a tool intended to inspect BPF programs and maps. It can
24 iterate over all programs and maps in the system and print basic information
27 The main use-case `bpf_inspect.py`_ covers is to show BPF programs of types
29 programs via ``freplace``/``fentry``/``fexit`` mechanisms, since there is no
35 List BPF programs (full names are obtained from BTF)::
49 Find BPF programs attached to BPF program ``test_pkt_access``::
62 are multiple other tracing and ext programs attached to functions in
80 drgn script to list BPF programs or maps and their properties
90 prog (p) list BPF programs
97 information about BPF programs, maps and other objects.
|
| D | bpf_prog_run.rst | 4 Running BPF programs from userspace
7 This document describes the ``BPF_PROG_RUN`` facility for running BPF programs
20 can be used to unit test BPF programs against user-supplied context objects, and
21 as way to explicitly execute programs in the kernel for their side effects. The
25 The ``BPF_PROG_RUN`` command can be used to execute BPF programs of the
46 execute the program and return the results to userspace. Note that programs will
49 returned to userspace. A separate mode for live execution of XDP programs is
52 Running XDP programs in "live frame mode"
55 The ``BPF_PROG_RUN`` command has a separate mode for running live XDP programs,
56 which can be used to execute XDP programs in a way where packets will actually
[all …]
|
| D | bpf_licensing.rst | 61 Using BPF programs in the Linux kernel
75 modules. BPF programs can be proprietary if they don't use "GPL only" BPF
83 and struct_ops BPF programs are implicitly calling "GPL only" functions.
84 The same restriction applies to BPF programs that call kernel functions
87 Packaging BPF programs with user space applications
90 Generally, proprietary-licensed applications and GPL licensed BPF programs
92 separate executable processes. This applies to both cBPF and eBPF programs.
|
| D | prog_lsm.rst | 8 These BPF programs allow runtime instrumentation of the LSM hooks by privileged
23 eBPF programs that use Documentation/bpf/btf.rst do not need to include kernel
51 build environment matches the environment the BPF programs are
54 The ``vmlinux.h`` can then simply be included in the BPF programs without
57 The eBPF programs can be declared using the``BPF_PROG``
98 eBPF programs can be loaded with the :manpage:`bpf(2)` syscall's
120 The LSM allows attachment of eBPF programs as LSM hooks using :manpage:`bpf(2)`
|
| D | prog_sk_lookup.rst | 40 Multiple programs can be attached to one network namespace. Programs will be
46 The attached BPF sk_lookup programs run whenever the transport layer needs to
52 The attached BPF programs must return with either ``SK_PASS`` or ``SK_DROP``
65 When multiple programs are attached, the end result is determined from return
66 codes of all the programs according to the following rules:
74 4. If all programs returned ``SK_PASS`` and none of them selected a socket,
|
| D | map_sockmap.rst | 28 These maps may have BPF programs attached to them, specifically a parser program
36 ``sk_psock`` inherits the programs that are attached to the map.
40 in having multiple parser programs the update will return an EBUSY error.
42 The supported programs to attach to these maps are:
55 programs to the same map.
57 The attach types for the map programs are:
65 programs: ``bpf_msg_apply_bytes()`` and ``bpf_msg_cork_bytes()``. With
66 ``bpf_msg_apply_bytes()`` BPF programs can tell the infrastructure how many
73 available to ``BPF_PROG_TYPE_SK_MSG`` BPF programs to pull in data and set the
89 This helper is used in programs implementing policies at the socket level. If
[all …]
|
| D | map_cgroup_storage.rst | 9 storage. It is only available with ``CONFIG_CGROUP_BPF``, and to programs that
10 attach to cgroups; the programs are made available by the same Kconfig. The
39 ``struct bpf_cgroup_storage_key``, then programs of different attach types
49 can be accessed by multiple programs across different CPUs, and user should
140 program, sharing of this cgroup's storage with other BPF programs were
143 Since Linux 5.9, storage can be shared by multiple programs. When a program is
|
| /linux-6.6.21/kernel/bpf/preload/ |
| D | Kconfig | 15 This builds kernel module with several embedded BPF programs that are
17 useful in debugging and introspection of BPF programs and maps.
24 This builds bpf_preload kernel module with embedded BPF programs for
|
| /linux-6.6.21/drivers/hid/bpf/ |
| D | Kconfig | 10 This option allows to support eBPF programs on the HID subsystem.
11 eBPF programs can fix HID devices in a lighter way than a full
|
| /linux-6.6.21/Documentation/networking/ |
| D | atm.rst | 8 several user-mode programs are required to assist the kernel. These
9 programs and related material can be found via the ATM on Linux Web
|
| /linux-6.6.21/drivers/media/radio/wl128x/ |
| D | Kconfig | 12 In order to control your radio card, you will need to use programs
14 this API and pointers to "v4l2" programs may be found at
|
| /linux-6.6.21/kernel/bpf/ |
| D | Kconfig | 38 Enable the bpf() system call that allows to manipulate BPF programs
47 BPF programs are normally handled by a BPF interpreter. This option
50 programs.
98 Enables instrumentation of the security hooks with BPF programs for
|
| /linux-6.6.21/Documentation/bpf/standardization/ |
| D | abi.rst | 19 * R0: return value from function calls, and exit value for BPF programs
24 R0 - R5 are scratch registers and BPF programs needs to spill/fill them if
|
| /linux-6.6.21/drivers/media/test-drivers/vidtv/ |
| D | vidtv_channel.c | 419 struct vidtv_psi_table_pat_program *programs = NULL; in vidtv_channel_si_init() local
432 programs = vidtv_channel_pat_prog_cat_into_new(m); in vidtv_channel_si_init()
433 if (!programs) in vidtv_channel_si_init()
458 programs->service_id); in vidtv_channel_si_init()
463 vidtv_psi_pat_program_assign(m->si.pat, programs); in vidtv_channel_si_init()
495 vidtv_psi_pat_program_destroy(programs); in vidtv_channel_si_init()
|
| /linux-6.6.21/LICENSES/exceptions/ |
| D | GCC-exception-2.0 | 14 compiled version of this file into combinations with other programs, and to
15 distribute those programs without any restriction coming from the use of
|
| /linux-6.6.21/Documentation/ABI/testing/ |
| D | sysfs-devices | 16 Or rely on the uevent messages to notify programs of
22 programs must be able to handle such occurrences.
|
| /linux-6.6.21/Documentation/trace/ |
| D | user_events.rst | 17 Typically programs will register a set of events that they wish to expose to
115 User programs are encouraged to use clearly sized types like u32.
120 This allows user programs to describe custom structs out to tools, if required.
140 event (in both user and kernel space). User programs should use a separate file
190 in realtime. This allows user programs to only incur the cost of the write() or
194 tools attach/detach from the event. User programs simply check if the bit is set
236 User programs might have well known structs that they wish to use to emit out
248 It's advised for user programs to do the following::
|
12345678910>>...14