Searched full:variables (Results 1 – 25 of 155) sorted by relevance
1234567
| /Documentation/filesystems/ |
| D | efivarfs.rst | 8 using entries in sysfs to maintain EFI variables. The old sysfs EFI
9 variables code only supported variables of up to 1024 bytes. This
11 removed before any full releases. Since variables can now be larger
14 Variables can be created, deleted and modified with the efivarfs
22 UEFI variables causes the system firmware to fail to POST, efivarfs
23 files that are not well-known standardized variables are created
|
| D | gfs2-uevents.rst | 22 The ADD uevent has two environment variables: SPECTATOR=[0|1]
31 has the same environment variables as the ADD uevent. The ONLINE
32 uevent, along with the two environment variables for spectator and
46 two environment variables, JID= which specifies the journal id which
54 without checking the environment variables to discover the state, we
78 Information common to all GFS2 uevents (uevent environment variables)
|
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 2 Shadow Variables
5 Shadow variables are a simple way for livepatch modules to associate
9 to allocate/add and remove/free shadow variables to/from their parents.
17 variables may attach to the same parent object, but their numeric
26 A hashtable references all shadow variables. These references are
85 * klp_shadow_free_all() - detach and free all <_, id> shadow variables
111 be easiest to align their shadow variables lifetimes to the same
167 variables alongside their parent objects. Or a livepatch fix may
168 require shadow variables for only a subset of parent object instances.
170 shadow variables to parents already in-flight.
[all …]
|
| D | api.rst | 14 Shadow Variables
|
| D | cumulative-patches.rst | 96 - There is no special handling of shadow variables. Livepatch authors
101 A good practice might be to remove shadow variables in the post-unpatch
|
| /Documentation/ABI/removed/ |
| D | sysfs-firmware-efi-vars | 5 EFI variables. For more information on EFI variables,
|
| /Documentation/ABI/testing/ |
| D | sysfs-uevent | 6 Enable passing additional variables for synthetic uevents that
37 with existing variables.
43 This generates synthetic uevent including these variables::
|
| D | sysfs-secvar | 5 secureboot, thereby secure variables. It exposes interface
6 for reading/writing the secure variables
11 Description: This directory lists all the secure variables that are supported
62 implementation provides variables to populate it, which at
|
| D | sysfs-class-devfreq-event | 6 This allows accessing various devfreq-event specific variables.
|
| /Documentation/core-api/ |
| D | local_ops.rst | 14 those local variables across CPUs when the order of memory writes matters.
66 * Variables touched by local ops must be per cpu variables.
67 * *Only* the CPU owner of these variables must write to them.
69 to update its ``local_t`` variables.
81 * Reads of these variables can be done from any CPU, because updates to
82 "``long``", aligned, variables are always atomic. Since no memory
84 variable can be read when reading some *other* cpu's variables.
|
| D | this_cpu_ops.rst | 9 variables associated with the *currently* executing processor. This is
119 Per cpu variables are used for performance reasons. Bouncing cache
122 variables no concurrent cache line updates take place. The price that
148 Per cpu variables and offsets
151 Per cpu variables have *offsets* to the beginning of the per cpu
275 If you use the variables as intended, this_cpu_ops() are guaranteed to
312 the following scenario that occurs because two per cpu variables
|
| /Documentation/networking/ |
| D | netfilter-sysctl.rst | 4 Netfilter Sysfs variables
7 /proc/sys/net/netfilter/* Variables:
|
| D | ioam6-sysctl.rst | 4 IOAM6 Sysfs variables
8 /proc/sys/net/conf/<iface>/ioam6_* variables:
|
| D | mpls-sysctl.rst | 4 MPLS Sysfs variables
7 /proc/sys/net/mpls/* Variables:
|
| D | seg6-sysctl.rst | 4 Seg6 Sysfs variables
8 /proc/sys/net/conf/<iface>/seg6_* variables:
|
| D | xfrm_sysctl.rst | 7 /proc/sys/net/core/xfrm_* Variables:
|
| D | mptcp-sysctl.rst | 4 MPTCP Sysfs variables
7 /proc/sys/net/mptcp/* Variables
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | u-boot.yaml | 13 Device configuration is stored as a set of environment variables that are
27 Broadcom stores environment variables inside a U-Boot partition. They
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | u-boot,env.yaml | 7 title: U-Boot environment variables layout
10 U-Boot uses environment variables to store device parameters and
24 Variables can be defined as NVMEM device subnodes.
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | brcm,nvram.yaml | 11 variables. It is used for storing device configuration, booting parameters
17 NVRAM variables can be defined as NVMEM device subnodes.
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_overview.rst | 21 global variables and work with BPF programs.
36 completely independent), BPF maps, and global variables. The global
37 variables are shared between all BPF programs, which allows them to cooperate on
46 object file and discovers BPF maps, BPF programs, and global variables. After
49 global variables, etc.) before all the entities are created and loaded.
62 packets, or updating BPF maps and global variables that can be read from user
102 global variables. The skeleton code memory maps global variables as a struct
|
| /Documentation/trace/ |
| D | histogram-design.rst | 76 histogram val and key in the histogram (variables are also included
354 Variables chapter
357 Variables allow data from one hist trigger to be saved by one hist
370 In terms of the histogram data structures, variables are implemented
569 .vars containing the current value of the variables associated with | |
703 event_name variables are also set.
736 location. Note also that the output shows that variables live in the
784 variables and values, they actually live in a separate hist_data
867 variables specified in the wakeup_latency() trace action, and use
873 variables. In this case, $wakeup_lat is obviously a variable, but
[all …]
|
| /Documentation/kbuild/ |
| D | kconfig.rst | 39 Environment variables
42 Environment variables for ``*config``:
70 Environment variables for ``{allyes/allmod/allno/rand}config``:
108 Environment variables for ``randconfig``:
147 Environment variables for ``syncconfig``:
255 Environment variables:
|
| D | kconfig-macro-language.rst | 50 Variables chapter
59 There are two types of variables: simply expanded variables and recursively
60 expanded variables.
88 In fact, recursively expanded variables and user-defined functions are the same
|
| /Documentation/security/ |
| D | self-protection.rst | 70 Function pointers and sensitive variables must not be writable
76 variables must be reduced to an absolute minimum.
78 Many such variables can be made read-only by setting them "const"
83 For variables that are initialized once at ``__init`` time, these can
86 What remains are variables that are updated rarely (e.g. GDT). These
157 is the presence of a stack canary between the stack variables and the
|
1234567