Searched full:variable (Results 1 – 25 of 486) sorted by relevance
12345678910>>...20
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 8 unmodified. The shadow variable API described in this document is used
14 used to describe shadow variable version, class or type, etc. More
29 * The klp_shadow variable data structure encapsulates both tracking
40 klp_shadow_get_or_alloc() are zeroing the variable by default.
46 to do actions that can be done only once when a new variable is allocated.
48 * klp_shadow_get() - retrieve a shadow variable data pointer
51 * klp_shadow_alloc() - allocate and add a new shadow variable
60 - allocate a new shadow variable
61 - initialize the variable using a custom constructor and data when provided
64 * klp_shadow_get_or_alloc() - get existing or alloc a new shadow variable
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-secvar | 18 This determines the format of the variable and the accepted
19 format of variable updates.
25 version number in the SB_VERSION variable in the keystore, and
27 "ibm,plpks-sb-unknown" if there is no SB_VERSION variable.
29 What: /sys/firmware/secvar/vars/<variable name>
32 Description: Each secure variable is represented as a directory named as
33 <variable_name>. The variable name is unique and is in ASCII
41 variable. In other words, it represents the size of the data.
46 Description: A read-only file containing the value of the variable. The size
47 of the file represents the maximum size of the variable data.
[all …]
|
| D | sysfs-class-tee | 13 space if the variable is absent. The primary purpose
14 of this variable is to let systemd know whether
|
| D | sysfs-uevent | 26 variable.
29 ``SYNTH_UUID=0`` environment variable automatically.
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 23 The macro language replaces the variable references with their expanded form,
53 Like in Make, a variable in Kconfig works as a macro variable. A macro
54 variable is expanded "in place" to yield a text string that may then be
55 expanded further. To get the value of a variable, enclose the variable name in
56 $( ). The parentheses are required even for single-letter variable names; $X is
62 A simply expanded variable is defined using the := assignment operator. Its
66 A recursively expanded variable is defined using the = assignment operator.
67 Its righthand side is simply stored as the value of the variable without
68 expanding it in any way. Instead, the expansion is performed when the variable
72 variable. The righthand side of += is expanded immediately if the lefthand
[all …]
|
| D | kconfig.rst | 45 This environment variable can be used to specify a default kernel config
49 This environment variable specifies a list of config files which can be
59 This environment variable makes Kconfig warn about all unrecognized
74 use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
89 (usually a subset of all) preset config symbols. These variable
116 This variable can be used to skew the probabilities. This variable can
150 If this variable has a non-blank value, it prevents silent kernel
154 This environment variable can be set to specify the path & name of the
158 This environment variable can be set to specify the path & name of the
207 It is possible to select different color themes using the variable
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-uevent.rst | 23 Variable Name: DM_TARGET
30 Variable Name: DM_ACTION
39 Variable Name: DM_SEQNUM
46 Variable Name: DM_PATH
54 Variable Name: DM_NR_VALID_PATHS
61 Variable Name: DM_NAME
68 Variable Name: DM_UUID
|
| /Documentation/devicetree/bindings/clock/ |
| D | arm,syscon-icst.yaml | 37 Integrator/AP 22 1 Bit 8 0, rest variable
40 Integrator/AP 46 3 Bit 8 0, rest variable
46 Integrator/CP 22 variable Bit 8 0, rest variable
49 Integrator/CP 22 variable Bit 8 0, rest variable
|
| /Documentation/trace/ |
| D | histogram-design.rst | 89 indicates which type of field it is - key, value, variable, variable
377 map_elt specifically designed to store and retrieve variable values.
378 The diagram below shows those new elements and adds a new variable
379 entry, ts0, corresponding to the ts0 variable in the sched_waking
446 variable. For a normal val hist_field, .flags is just 0 (modulo | | |
447 modifier flags), but if the value is defined as a variable, the .flags | | |
451 into the tracing_map_elts' .vars[] array containing variable values. | | |
452 This idx is used whenever the value of the variable is set or read. | | |
453 The map_elt.vars idx assigned to the given variable is assigned and | | |
465 or val and the .vars[] members point to the value of a variable. The | | |
[all …]
|
| /Documentation/networking/ |
| D | netif-msg.rst | 18 integer variable that controls the debug message level. The message
34 Initially this message level variable was uniquely named in each driver
53 - Retaining the per-driver integer variable "debug" as a module
56 - Adding a per-interface private variable named "msg_enable". The
57 variable is a bit map rather than a level, and is initialized as::
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-priority.rst | 40 variable where the driver stores the current priority.
43 an enum v4l2_priority variable and call :ref:`VIDIOC_S_PRIORITY <VIDIOC_G_PRIORITY>` ioctl
44 with a pointer to this variable.
83 On success 0 is returned, on error -1 and the ``errno`` variable is set
|
| /Documentation/core-api/ |
| D | this_cpu_ops.rst | 14 this_cpu operations add a per cpu variable offset to the processor
16 operating on the per cpu variable.
31 Access to the variable without the lock prefix is not synchronized but
34 processor should be accessing that variable and therefore there are no
134 Takes the offset of a per cpu variable (&x !) and returns the address
135 of the per cpu variable that belongs to the currently executing
166 cpu variable. Most this_cpu operations take a cpu variable.
172 &x and hence p is the *offset* of a per cpu variable. this_cpu_ptr()
173 takes the offset of a per cpu variable which makes this look a bit
230 preemption. If a per cpu variable is not used in an interrupt context
[all …]
|
| D | local_ops.rst | 39 Local atomic operations only guarantee variable modification atomicity wrt the
72 different CPU between getting the per-cpu variable and doing the
79 * Reading the local cpu variable will provide the current copy of the
80 variable.
84 variable can be read when reading some *other* cpu's variables.
105 access to the per cpu variable. For instance::
131 the ``local_t`` variable as a counter of bytes written in a buffer: there should
160 /* This is what incrementing the variable would look like within a
|
| /Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 108 In order to load SSDTs from an EFI variable the ``"efivar_ssdt=..."`` kernel
110 The argument for the option is the variable name to use. If there are multiple
114 In order to store the AML code in an EFI variable the efivarfs filesystem can be
119 EFI variable. Updating a file in /sys/firmware/efi/efivars will update the EFI
120 variable. Please note that the file name needs to be specially formatted as
122 represent the attributes of the EFI variable (see EFI_VARIABLE_MASK in
127 variable with the content from a given file::
|
| /Documentation/filesystems/ |
| D | efivarfs.rst | 4 efivarfs - a (U)EFI variable filesystem
29 When a content of an UEFI variable in /sys/firmware/efi/efivars is
31 4 bytes of the output represent the UEFI variable attributes,
|
| /Documentation/devicetree/bindings/net/ |
| D | samsung-sxgbe.txt | 7 These interrupts are ordered by fixed and follows variable
11 index 1 to 25 - 8 variable transmit interrupts, variable 16 receive interrupts
|
| /Documentation/fb/ |
| D | api.rst | 51 additional information, which are stored in the variable screen information
89 stored in the variable screen information grayscale field.
94 specified by the variable screen information bpp field.
105 specified by the variable screen information bpp field.
119 Each component is stored in a macropixel according to the variable screen
128 Each pixel value is stored in the number of bits reported by the variable
136 Each component is stored in a macropixel according to the variable screen
142 identifier stored in the variable screen information grayscale field.
222 To modify variable information, applications call the FBIOPUT_VSCREENINFO
|
| /Documentation/dev-tools/ |
| D | kmsan.rst | 49 Local variable uninit created at:
60 The report says that the local variable ``uninit`` was created uninitialized in
62 where this variable was created.
66 uninitialized in the local variable, as well as the stack where the value was
141 When a new variable is allocated on the stack, it is poisoned by default by
142 instrumentation code inserted by the compiler (unless it is a stack variable
174 variable (for locals).
176 When an uninitialized variable is allocated on stack or heap, a new origin
177 value is created, and that variable's origin is filled with that value. When a
195 same four-byte chunk. In this case every write to either variable updates the
[all …]
|
| D | coccinelle.rst | 79 ``org``. The mode to use is specified by setting the MODE variable with
126 To enable verbose messages set the V= variable, for example::
134 the parallelism, set the J= variable. For example, to run across 4 CPUs::
154 The optional make variable COCCI can be used to check a single
155 semantic patch. In that case, the variable must be initialized with
178 C variable is used by the makefile to select which files to work with.
179 This variable can be used to run scripts for the entire kernel, a
183 passed to the C variable to check files that make considers
188 The value 2 is passed to the C variable to check files regardless of
197 COCCI variable may additionally be used to only apply a single
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | arm,scpi.yaml | 123 "arm,scpi-dvfs-clocks" - all the clocks that are variable and index
130 "arm,scpi-variable-clocks" - all the clocks that are variable and
138 - arm,scpi-variable-clocks
197 compatible = "arm,scpi-variable-clocks";
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | gdb-kernel-debugging.rst | 162 function lx_module -- Find module by name and return the module variable
163 function lx_per_cpu -- Return per-cpu variable
164 function lx_task_by_pid -- Find Linux task by PID and return the task_struct variable
165 function lx_thread_info -- Calculate Linux thread_info from task variable
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 7 C programmers have often taken volatile to mean that the variable could be
11 as a sort of easy atomic variable, which they are not. The use of volatile in
62 when the processor is busy-waiting on the value of a variable. The right
85 - The jiffies variable is special in that it can have a different value
|
| /Documentation/translations/zh_TW/dev-tools/ |
| D | gdb-kernel-debugging.rst | 158 function lx_module -- Find module by name and return the module variable
159 function lx_per_cpu -- Return per-cpu variable
160 function lx_task_by_pid -- Find Linux task by PID and return the task_struct variable
161 function lx_thread_info -- Calculate Linux thread_info from task variable
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-func-poll.rst | 47 a value of zero, on failure it returns -1 and the ``errno`` variable is
58 timed out. On error -1 is returned, and the ``errno`` variable is set
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-poll.rst | 50 a value of zero, on failure it returns -1 and the ``errno`` variable is
60 is returned, and the ``errno`` variable is set appropriately:
|
12345678910>>...20