| /linux/tools/net/sunrpc/xdrgen/generators/ |
| H A D | program.py | 4 """Generate code for an RPC program's procedures"""
13 environment: Environment, program: str, version: _RpcVersion
17 print(template.render(program=program.upper()))
34 environment: Environment, program: str, version: _RpcVersion
45 print(template.render(program=program, argument=argument))
55 print(template.render(program=program, result=result))
59 environment: Environment, program
[all...] |
| /linux/drivers/pwm/ |
| H 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()
168 program[0] = LOAD | 0x00; /* LOAD 0x00 */ in stmpe_24xx_pwm_config()
191 /* Run the old program */ in stmpe_24xx_pwm_config()
198 program[0] = LOAD | value; in stmpe_24xx_pwm_config()
199 program[1] = 0x0000; in stmpe_24xx_pwm_config()
201 /* STMPE2401 need a complex program */ in stmpe_24xx_pwm_config()
212 program[ in stmpe_24xx_pwm_config()
[all...] |
| /linux/Documentation/bpf/ |
| H 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
59 calling ``bpf_sk_assign()`` BPF helper. Typically, the program looks up a socket
62 selection. Selecting a socket only takes effect if the program has terminated
68 1. If any program returne
[all...] |
| H 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
46 execute the program and return the results to userspace. Note that programs will
48 will not actually be redirected or dropped, the program return code will just be
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),
67 - When executing an XDP program in live frame mode, the result of the execution
69 operation indicated by the program'
[all...] |
| H 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)
131 for a single ``CGROUP_STORAGE`` map, there can be at most one program loaded
132 that uses the map. A program may be attached to multiple cgroups or have
137 non-per-CPU) and the BPF program during load verification time. As a result,
138 each map can only be used by one BPF program an
[all...] |
| H 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
38 * ``1`` - success, continue with next BPF program in the cgroup chain.
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,
91 When the ``optval`` is greater than the ``PAGE_SIZE``, the BPF program
96 done by the BPF program t
[all...] |
| H A D | bpf_iterators.rst | 10 iterator *program type* and *open-coded* BPF iterators. The former is
11 a stand-alone BPF program type which, when attached and activated by user,
14 functionality and available across multiple BPF program types. Open-coded
16 more flexibility and control to all other BPF program types. BPF iterator
19 program, backed by seq_file functionality. Both are useful depending on
22 When adding a new BPF iterator program, it is expected that similar
39 bpf_iter_<type> state needs to live on BPF program stack, so make sure it's
111 verifier can claim safety of the overall program logic.
141 A BPF iterator is a type of BPF program that allows users to iterate over
152 A BPF program i
[all...] |
| H 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
|
| H 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
78 has to be overridden BPF program can set ``file_pos`` to zero before calling
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 i
[all...] |
| H 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 ca
[all...] |
| H 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
[all...] |
| H A D | map_sockmap.rst | 14 the result of a BPF (verdict) program with the help of the BPF helpers
28 These maps may have BPF programs attached to them, specifically a parser program
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
[all...] |
| /linux/Documentation/userspace-api/ |
| H 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/ |
| H 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()
106 /* Enter program mode */ 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()
285 /* Enter program mode */ in sysconfig_ops_write_init()
288 dev_err(dev, "Failed to go to program mod in sysconfig_ops_write_init()
355 struct gpio_desc *program, *init, *done; sysconfig_probe() local
[all...] |
| /linux/tools/bpf/bpftool/Documentation/ |
| H 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
[all...] |
| H A D | bpftool-prog.rst | 77 Output will start with program ID followed by program type and zero or more
81 the total time spent running the program, and the number of times it was
84 program run. Activation or deactivation of the feature is performed via the
99 *PROG* must match a single program.
113 Dump jited image (host machine code) of the program.
116 be disassembled and printed to stdout. *PROG* must match a single program
126 Pin program *PROG* as *FILE*.
132 Load bpf program(s) from binary *OBJ* and pin as *PATH*. **bpftool prog
133 load** pins only the first program fro
[all...] |
| H 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/ |
| H A D | hid-bpf.rst | 38 HID-BPF allows the userspace program to load the program itself, ensuring we
48 We can reduce this burden by providing an eBPF program instead. Once such a
49 program has been verified by the user, we can embed the source code into the
50 kernel tree and ship the eBPF program and load it directly instead of loading
80 events into wheel events. Also, the userspace program can set/unset the haptic
96 kernel/bpf program because we can intercept any incoming command.
119 program.
128 When a BPF program needs to emit input events, it needs to talk with the HID
162 A ``hid_device_event`` is calling a BPF program whe
261 ``SEC("struct_ops/hid_device_event")``Effect of a HID-BPF program global() argument
277 ``SEC("syscall")``Effect of a HID-BPF program global() argument
291 ``SEC("struct_ops/hid_rdesc_fixup")``Effect of a HID-BPF program global() argument
[all...] |
| /linux/security/tomoyo/ |
| H 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
248 char *domainname = strstr(program, " from "); in tomoyo_write_transition_control()
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 in tomoyo_write_transition_control()
299 tomoyo_scan_transition(const struct list_head * list,const struct tomoyo_path_info * domainname,const struct tomoyo_path_info * program,const char * last_name,const enum tomoyo_transition_type type) tomoyo_scan_transition() argument
346 tomoyo_transition_type(const struct tomoyo_policy_namespace * ns,const struct tomoyo_path_info * domainname,const struct tomoyo_path_info * program) tomoyo_transition_type() argument
[all...] |
| /linux/Documentation/networking/ |
| H 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/ |
| H A D | vidtv_psi.c | 895 struct vidtv_psi_table_pat_program *program; in vidtv_psi_pat_program_init() local
898 program = kzalloc(sizeof(*program), GFP_KERNEL); in vidtv_psi_pat_program_init()
899 if (!program) in vidtv_psi_pat_program_init()
902 program->service_id = cpu_to_be16(service_id); in vidtv_psi_pat_program_init()
905 program->bitfield = cpu_to_be16((RESERVED << 13) | program_map_pid); in vidtv_psi_pat_program_init()
906 program->next = NULL; in vidtv_psi_pat_program_init()
912 head->next = program; in vidtv_psi_pat_program_init()
915 return program; in vidtv_psi_pat_program_init()
936 struct vidtv_psi_table_pat_program *program; in vidtv_psi_pat_program_assign() local
1128 struct vidtv_psi_table_pat_program *program = pat->program; vidtv_psi_pmt_get_pid() local
1511 struct vidtv_psi_table_pat_program *program; vidtv_psi_pmt_create_sec_for_each_pat_entry() local
[all...] |
| /linux/Documentation/admin-guide/nfs/ |
| H 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/Documentation/misc-devices/ |
| H 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)::
|
| /linux/Documentation/admin-guide/ |
| H A D | java.rst | 8 other program after you have done the following:
60 You, too, need the little program after the script. Compile like::
66 Both the javawrapper shellscript and the javaclassname program
171 * This program is free software; you can redistribute it and/or modify
176 * This program is distributed in the hope that it will be useful,
182 * along with this program; if not, write to the Free Software
210 #define seek_error() error("%s: Cannot seek\n", program)
211 #define corrupt_error() error("%s: Class file corrupt\n", program)
212 #define eof_error() error("%s: Unexpected end of file\n", program)
213 #define utf8_error() error("%s: Only ASCII 1-255 supported\n", program);
[all...] |
| /linux/tools/perf/Documentation/ |
| H A D | cpu-and-latency-overheads.txt | 4 For a single-threaded program, or a program running on a single-core machine,
5 these notions are the same. However, for a multi-threaded/multi-process program
16 latency of a single interactive program build.
18 consider a program that executes function 'foo' for 9 seconds with 1 thread,
22 running time of the program looking at the (wrong in this case) CPU overhead,
|