| /linux/tools/net/sunrpc/xdrgen/generators/ |
| A D | program.py | 13 environment: Environment, program: str, version: _RpcVersion 17 print(template.render(program=program.upper())) 45 print(template.render(program=program, argument=argument)) 55 print(template.render(program=program, result=result)) 69 print(template.render(program=program, argument=argument)) 83 print(template.render(program=program, result=result)) 97 print(template.render(program=program, argument=argument)) 111 print(template.render(program=program, result=result)) 146 self.environment, program, version, 151 self.environment, program, version, [all …]
|
| /linux/drivers/pwm/ |
| A D | pwm-stmpe.c | 102 u16 program[3] = { in stmpe_24xx_pwm_config() local 157 program[0] = SMAX; /* off all the time */ in stmpe_24xx_pwm_config() 160 program[0] = LOAD | 0xff; /* LOAD 0xff */ in stmpe_24xx_pwm_config() 165 program[0] = SMIN; /* on all the time */ in stmpe_24xx_pwm_config() 198 program[0] = LOAD | value; in stmpe_24xx_pwm_config() 199 program[1] = 0x0000; in stmpe_24xx_pwm_config() 215 program[1] = BRANCH; in stmpe_24xx_pwm_config() 220 pwm->hwpwm, value, last, program[0], program[1], in stmpe_24xx_pwm_config() 221 program[2]); in stmpe_24xx_pwm_config() 231 value = (program[i] >> 8) & 0xff; in stmpe_24xx_pwm_config() [all …]
|
| /linux/Documentation/bpf/ |
| A D | prog_sk_lookup.rst | 4 BPF sk_lookup program 7 BPF sk_lookup program type (``BPF_PROG_TYPE_SK_LOOKUP``) introduces programmability 11 When invoked BPF sk_lookup program can select a socket that will receive the 19 BPF sk_lookup program type was introduced to address setup scenarios where 36 BPF sk_lookup program can be attached to a network namespace with 53 verdict code. As for other BPF program types that are network filters, 58 A BPF sk_lookup program can also select a socket to receive the packet by 62 selection. Selecting a socket only takes effect if the program has terminated 68 1. If any program returned ``SK_PASS`` and selected a valid socket, the socket 72 3. If any program returned ``SK_DROP``, and no program returned ``SK_PASS`` and [all …]
|
| A D | bpf_prog_run.rst | 19 execute a BPF program in the kernel and return the results to userspace. This 44 object and (for program types operating on network packets) a buffer containing 45 the packet data that the BPF program will operate on. The kernel will then 57 be processed by the kernel after the execution of the XDP program as if they 59 ``BPF_F_TEST_XDP_LIVE_FRAMES`` flag when supplying an XDP program to 63 XDP program many times (suitable for, e.g., running as a traffic generator), 69 operation indicated by the program's return code (drop the packet, redirect 80 the regular (non-live) mode. The XDP program will be executed as though the 86 because the program execution is not happening in driver context, an 95 the kernel executes the XDP program repeatedly, each invocation getting a [all …]
|
| A D | bpf_iterators.rst | 48 program verified and loaded by the kernel. 54 program is obtained using ``bpf_link_create()``, and the program callback is 121 so they won't go away when the BPF program runs. 157 the program is a BPF iterator program to iterate all files from all tasks. The 158 context of the program is ``bpf_iter__task_file`` struct. 160 The user space program invokes the BPF iterator program running in the kernel 334 The whole program looks like the following code: 398 The following lines are the output of the program. 422 BPF program to pass a *pid* to the BPF program. 424 The BPF program would look like the following block. [all …]
|
| A D | map_cgroup_storage.rst | 11 storage is identified by the cgroup the program is attached to. 13 The map provide a local storage at the cgroup that the BPF program is attached 34 ``attach_type`` is the program's attach type. 42 To access the storage in a program, use ``bpf_get_local_storage``:: 67 int program(struct __sk_buff *skb) 102 int program(struct __sk_buff *skb) 132 that uses the map. A program may be attached to multiple cgroups or have 138 each map can only be used by one BPF program and each BPF program can only use 140 program, sharing of this cgroup's storage with other BPF programs were 153 However, the BPF program can still only associate with one map of each type [all …]
|
| A D | prog_cgroup_sockopt.rst | 7 ``BPF_PROG_TYPE_CGROUP_SOCKOPT`` program type can be attached to two 26 If BPF program sets ``optlen`` to -1, the control will be returned 62 the BPF program from the parent cgroup). 76 the programs are executed from the bottom up: B, A. First program 79 control will be passed to the second (A) program which will see the 82 Same for ``BPF_CGROUP_SETSOCKOPT``: if the program is attached to 85 then the next program in the chain (A) will see those changes, 96 done by the BPF program to the ``optval`` are ignored. 100 When the BPF program returns with the ``optlen`` greater than 102 buffers without any modifications that the BPF program might have [all …]
|
| A D | map_cgrp_storage.rst | 21 To access the storage in a program, use ``bpf_cgrp_storage_get``:: 32 The map is available to all program types. 37 A BPF program example with BPF_MAP_TYPE_CGRP_STORAGE:: 87 (1). ``BPF_MAP_TYPE_CGRP_STORAGE`` can be used by all program types while 88 ``BPF_MAP_TYPE_CGROUP_STORAGE_DEPRECATED`` is available only to cgroup program types 93 which is attached by a BPF program. 100 ``bpf_map_update_elem()`` to pre-allocate local storage before a BPF program 103 (4). ``BPF_MAP_TYPE_CGRP_STORAGE`` supports deleting local storage by a BPF program
|
| A D | prog_cgroup_sysctl.rst | 7 This document describes ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program type that 17 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program to a cgroup. 23 BPF program:: 49 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program must return one of the following 55 If program returns ``0`` user space will get ``-1`` from ``read(2)`` or 65 ``/proc/sys`` into provided by BPF program buffer; 68 sysctl into provided by BPF program buffer. This helper is available on both 83 BPF program sees sysctl value same way as user space does in proc filesystem, 98 See `test_sysctl_prog.c`_ for an example of BPF program in C that access 116 As with any cgroup-bpf program additional care should be taken if an [all …]
|
| A D | prog_lsm.rst | 15 The example shows an eBPF program that can be attached to the ``file_mprotect`` 24 headers for accessing information from the attached eBPF program's context. 25 They can simply declare the structures in the eBPF program and only specify 61 * ``"lsm/file_mprotect"`` indicates the LSM hook that the program must 63 * ``mprotect_audit`` is the name of the eBPF program 71 /* ret is the return value from the previous BPF program 93 eBPF program. 114 and the program can be loaded by including ``my_prog.skel.h`` and using 124 The program can be detached from the LSM hook by *destroying* the ``link`` 133 An example eBPF program can be found in
|
| A D | map_devmap.rst | 43 fails. This is so that the return value can be one of the XDP program return 75 from an eBPF program. Trying to call these functions from a kernel eBPF 76 program will result in the program failing to load and a verifier warning. 104 DEVMAPs can associate a program with a device entry by adding a ``bpf_prog.fd`` 106 access to both Rx device and Tx device. The program associated with the ``fd`` 108 When a program is associated with a device index, the program is run on an 170 The following code snippet shows a simple xdp_redirect_map program. This program 171 would work with a user space program that populates the devmap ``forward_map`` based 172 on ingress ifindexes. The BPF program (below) is redirecting packets using the 185 The following code snippet shows a BPF program that is broadcasting packets to
|
| A D | map_sockmap.rst | 14 the result of a BPF (verdict) program with the help of the BPF helpers 29 and a verdict program. The parser program determines how much data has been 31 verdict program is essentially the redirect program and can return a verdict 39 parse or verdict program. If adding a sock object to a map would result 59 - ``msg_parser`` program - ``BPF_SK_MSG_VERDICT``. 60 - ``stream_parser`` program - ``BPF_SK_SKB_STREAM_PARSER``. 61 - ``stream_verdict`` program - ``BPF_SK_SKB_STREAM_VERDICT``. 62 - ``skb_verdict`` program - ``BPF_SK_SKB_VERDICT``. 90 the message ``msg`` is allowed to pass (i.e., if the verdict BPF program 365 The following code snippet shows a sample parser program. [all …]
|
| /linux/Documentation/userspace-api/ |
| A D | ELF.rst | 10 "First" program header is the one with the smallest offset in the file: 13 "Last" program header is the one with the biggest offset in the file: 19 First PT_INTERP program header is used to locate the filename of ELF 25 Last PT_GNU_STACK program header defines userspace stack executability 31 ELF interpreter's last PT_GNU_PROPERTY program header is used (since 33 program header of an executable is used. Other PT_GNU_PROPERTY headers
|
| /linux/drivers/fpga/ |
| A D | lattice-sysconfig.c | 91 struct gpio_desc *program = priv->program; in sysconfig_gpio_refresh() local 97 gpiod_set_value(program, 1); in sysconfig_gpio_refresh() 107 gpiod_set_value(program, 0); in sysconfig_gpio_refresh() 128 struct gpio_desc *program = priv->program; in sysconfig_refresh() local 132 if (program && init && done) in sysconfig_refresh() 355 struct gpio_desc *program, *init, *done; in sysconfig_probe() local 370 program = devm_gpiod_get_optional(dev, "program", GPIOD_OUT_LOW); in sysconfig_probe() 371 if (IS_ERR(program)) in sysconfig_probe() 372 return dev_err_probe(dev, PTR_ERR(program), in sysconfig_probe() 385 priv->program = program; in sysconfig_probe()
|
| /linux/tools/bpf/bpftool/Documentation/ |
| A D | bpftool-cgroup.rst | 55 Output will start with program ID followed by attach type, attach flags and 56 program name. 67 with absolute cgroup path, followed by program ID, attach type, attach 68 flags and program name. 75 Attach program *PROG* to the cgroup *CGROUP* with attach type *ATTACH_TYPE* 79 bpf program, the program in this cgroup yields to sub-cgroup program; 80 **multi** if a sub-cgroup installs some bpf program, that cgroup program 81 gets run in addition to the program in this cgroup. 83 Only one program is allowed to be attached to a cgroup with no attach flags 84 or the **override** flag. Attaching another program will release old [all …]
|
| A D | bpftool-prog.rst | 76 Output will start with program ID followed by program type and zero or more 98 *PROG* must match a single program. 112 Dump jited image (host machine code) of the program. 125 Pin program *PROG* as *FILE*. 141 **offload_dev** *NAME* is specified program will be loaded onto given 148 case, only the link (representing the program attached to its hook) is 154 for that program instead. 160 Attach bpf program *PROG* (with type specified by *ATTACH_TYPE*). Most 177 Run BPF program *PROG* in the kernel testing infrastructure for BPF, 202 perform checks on program types. [all …]
|
| A D | bpftool-net.rst | 37 List bpf program attachments in the kernel networking subsystem. 41 attachments are implemented, i.e., for program types **BPF_PROG_TYPE_XDP**, 52 The current output will start with all xdp program attachments, followed by 53 all tcx, netkit, then tc class/qdisc bpf program attachments, then 62 Attach bpf program *PROG* to network interface *NAME* with type specified 63 by *ATTACH_TYPE*. Previously attached bpf program can be replaced by the 76 Detach bpf program attached to network interface *NAME* with type specified 77 by *ATTACH_TYPE*. To detach bpf program, same *ATTACH_TYPE* previously used
|
| /linux/Documentation/hid/ |
| A D | hid-bpf.rst | 38 HID-BPF allows the userspace program to load the program itself, ensuring we 119 program. 173 program has been loaded, it is not possible to overwrite it unless the program which 207 General overview of a HID-BPF program 245 Effect of a HID-BPF program 254 program is appended at the end of the list. 318 Attaching a bpf program to a device 344 component that loads the eBPF program. 434 fprintf(stderr, "can not attach HID-BPF program: %m\n"); 446 detach the program from the HID device. [all …]
|
| /linux/security/tomoyo/ |
| A D | domain.c | 231 && p1->program == p2->program; in tomoyo_same_transition_control() 247 char *program = param->data; in tomoyo_write_transition_control() local 255 domainname = program; in tomoyo_write_transition_control() 256 program = NULL; in tomoyo_write_transition_control() 258 if (program && strcmp(program, "any")) { in tomoyo_write_transition_control() 259 if (!tomoyo_correct_path(program)) in tomoyo_write_transition_control() 261 e.program = tomoyo_get_name(program); in tomoyo_write_transition_control() 262 if (!e.program) in tomoyo_write_transition_control() 280 tomoyo_put_name(e.program); in tomoyo_write_transition_control() 321 if (ptr->program && tomoyo_pathcmp(ptr->program, program)) in tomoyo_scan_transition() [all …]
|
| /linux/Documentation/networking/ |
| A D | xdp-rx-metadata.rst | 7 This document describes how an eXpress Data Path (XDP) program can access 31 An XDP program can use these kfuncs to read the metadata into stack 33 consumers, an XDP program can store it into the metadata area carried 52 An XDP program can store individual metadata items into this ``data_meta`` 61 program that redirects XDP frames into the ``AF_XDP`` socket (``XSK``) and 62 the final consumer. Thus the BPF program manually allocates a fixed number of 82 This is the path where the packets processed by the XDP program are passed 90 In the future, we'd like to support a case where an XDP program 98 program after the redirect. However, the final consumer doesn't have 104 currently supported, which has to be prepared by the initial XDP program [all …]
|
| /linux/drivers/media/test-drivers/vidtv/ |
| A D | vidtv_psi.c | 898 program = kzalloc(sizeof(*program), GFP_KERNEL); in vidtv_psi_pat_program_init() 899 if (!program) in vidtv_psi_pat_program_init() 915 return program; in vidtv_psi_pat_program_init() 941 program = p; in vidtv_psi_pat_program_assign() 948 program = program->next; in vidtv_psi_pat_program_assign() 1128 struct vidtv_psi_table_pat_program *program = pat->program; in vidtv_psi_pmt_get_pid() local 1135 while (program) { in vidtv_psi_pmt_get_pid() 1139 program = program->next; in vidtv_psi_pmt_get_pid() 1519 program = pat->program; in vidtv_psi_pmt_create_sec_for_each_pat_entry() 1523 program = program->next; in vidtv_psi_pmt_create_sec_for_each_pat_entry() [all …]
|
| /linux/include/trace/events/ |
| A D | sunrpc.h | 208 const char *program, 217 __string(program, program) 1443 u32 program, 1459 __entry->program = program; 1473 u32 program, 1489 __entry->program = program; 1503 u32 program, 1517 __entry->program = program; 1970 __string(program, program) 2454 __string(program, program) [all …]
|
| /linux/Documentation/admin-guide/nfs/ |
| A D | nfs-idmapper.rst | 34 This will direct all id_resolver requests to the program /usr/sbin/nfs.idmap. 47 program. If you would like to use your own program for a uid lookup then you 52 ``create id_resolver uid:* * /some/other/program %k %d 600`` 56 Notice that the new line was added above the line for the generic program. 57 request-key will find the first matching line and corresponding program. In 58 this case, /some/other/program will handle all uid lookups and 69 hand". This program takes two arguments, a serialized key and a key
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| A D | raw_tp_writable_reject_nbd_invalid.c | 13 const struct bpf_insn program[] = { in test_raw_tp_writable_reject_nbd_invalid() local 29 program, ARRAY_SIZE(program), in test_raw_tp_writable_reject_nbd_invalid()
|
| /linux/Documentation/misc-devices/ |
| A D | spear-pcie-gadget.rst | 30 and then program its various registers to configure it as a particular device 68 bar0 is SYSRAM1(E0800000). Always program bar size before bar 90 program vendor id as 0x104a:: 94 program device id as 0xCD80:: 98 program BAR0 size as 1MB:: 108 can also be made visible to PCIe host. E.g., if you program base address of UART 116 program interrupt type : INTA:: 142 if MSI is to be used as interrupt, program no of msi vector needed (say4)::
|