Searched full:programs (Results 1 – 25 of 246) sorted by relevance
12345678910
| /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 …]
|
| /Documentation/bpf/ |
| 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_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 | 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 | 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 | 5 LSM BPF Programs
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 | 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 | 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
|
| 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 | helpers.rst | 4 * `bpf-helpers(7)`_ maintains a list of helpers available to eBPF programs.
|
| /Documentation/trace/ |
| D | user_events.rst | 13 Programs can view status of the events via
17 Programs can also use /sys/kernel/tracing/dynamic_events to register and
22 Typically programs will register a set of events that they wish to expose to
96 allows programs to prevent themselves from being blocked when their event
103 tracepoint with a new unique id. Recording programs need to scan tracefs for
108 a hex string. Recording programs should ensure the tracepoint name starts with
148 User programs are encouraged to use clearly sized types like u32.
153 This allows user programs to describe custom structs out to tools, if required.
173 event (in both user and kernel space). User programs should use a separate file
177 to the event. If programs do not want auto-delete, they must use the
[all …]
|
| /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
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 11 Userspace programs can start to rely on these interfaces, but they must
15 Programs that use these interfaces are strongly encouraged to add their
|
| D | serial-console.rst | 125 Programs that want to do something with the virtual console usually
127 and your console is NOT the virtual console some programs will fail.
128 Those are programs that want to access the VT interface, and use
129 ``/dev/console instead of /dev/tty0``. Some of those programs are::
133 It should be fixed in modern versions of these programs though.
|
| D | abi-stable.rst | 6 Userspace programs are free to use these interfaces with no
|
| /Documentation/ABI/ |
| D | README | 4 interfaces should be used by userspace programs in different ways.
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
28 be marked stable. Programs that use these interfaces are
|
| /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.
|
| /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
|
| /Documentation/spi/ |
| D | spi-sc18is602.rst | 36 means that programs such as "cp" or "od", which automatically use large block
38 Programs such as dd, where the block size can be specified, should be used
|
| /Documentation/hid/ |
| D | hid-bpf.rst | 53 Note: distribution of eBPF programs and their inclusion in the kernel is not
132 In-tree HID-BPF programs and ``udev-hid-bpf``
149 Available types of programs
153 declare our programs.
189 User API data structures available in programs:
195 Available API that can be used in all HID-BPF struct_ops programs:
201 Available API that can be used in syscall HID-BPF programs or in sleepable HID-BPF struct_ops progr…
249 programs can be attached to the same device. If a HID-BPF struct_ops has a
258 Note that if there are multiple programs using the ``BPF_F_BEFORE`` flag,
264 Whenever a matching event is raised, the eBPF programs are called one after the other
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 15 CAP_SETUID is granted to programs running as root or those running as a non-root
27 especially since programs often only call setuid() to drop privileges to a
42 non-root programs can drop to even-lesser-privileged uids. This is especially
69 namespace and give programs in the tree setid capabilities. In this way,
70 programs in the tree could change to any desired UID/GID in the context of their
|
| /Documentation/kbuild/ |
| D | kbuild.rst | 89 Additional flags to be passed to $(HOSTCC) when building host programs.
93 Additional flags to be passed to $(HOSTCXX) when building host programs.
97 Additional flags to be passed to $(HOSTRUSTC) when building host programs.
106 the one the user wants to use for host programs.
108 If unset, it defaults to the flags passed when linking host programs.
112 Additional flags to be passed when linking host programs.
116 Additional libraries to link against when building host programs.
|
| D | headers_install.rst | 6 form suitable for use by userspace programs.
9 programs attempting to use kernel services. These kernel header files are
|
| D | makefiles.rst | 741 Composite Host Programs
744 Host programs can be made up based on composite objects.
745 The syntax used to define composite objects for host programs is
761 Note: The syntax <executable>-y is not permitted for host-programs.
763 Using C++ for host programs
766 kbuild offers support for host programs written in C++. This was
789 Using Rust for host programs
792 Kbuild offers support for host programs written in Rust. However,
806 Controlling compiler options for host programs
809 When compiling host programs, it is possible to set specific flags.
[all …]
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 7 programs and file capabilities. To prevent the parent program from
48 execve and can change the behavior of newly-executed programs.
|
12345678910