| /linux-6.12.1/drivers/gpu/drm/ci/ |
| D | test.yml | 25 variables:
41 variables:
57 variables:
76 variables:
95 variables:
104 variables:
114 variables:
124 variables:
141 variables:
156 variables:
[all …]
|
| D | build.yml | 18 variables:
29 variables:
38 variables:
65 variables:
77 variables:
89 variables:
107 variables:
|
| D | container.yml | 2 variables:
7 variables:
11 variables:
15 variables:
19 variables:
|
| /linux-6.12.1/include/xen/interface/ |
| D | platform.h | 23 /* IN variables. */
31 /* IN variables. */
48 /* IN variables. */
52 /* OUT variables. */
67 /* IN variables. */
76 /* IN variables. */
78 /* OUT variables. */
87 /* IN variables. */
98 /* IN variables. */
211 /* IN variables. */
[all …]
|
| /linux-6.12.1/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)
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/tools/testing/selftests/net/forwarding/ |
| D | README | 63 The forwarding selftests framework uses a number of variables that
65 various ways. A number of these variables can be overridden. The way these
66 overridable variables are specified is typically one of the following two
72 Any of these variables can be overridden. Notably net/forwarding/lib.sh and
73 net/lib.sh contain a number of overridable variables.
75 One way of overriding these variables is through the environment:
85 A way to customize variables in a persistent fashion is to create a file
88 assignments of variables whose value should be overridden.
|
| /linux-6.12.1/drivers/net/fddi/skfp/h/ |
| D | sba.h | 32 * Node variables
53 * Session variables
81 * variables for allocation actions
102 * SBA variables
108 * SBA state machine variables
118 * variables for the End Station Support
133 * variables for the ess bandwidth control
|
| /linux-6.12.1/drivers/firmware/qcom/ |
| D | Kconfig | 55 which is required to access UEFI variables on certain systems. If
66 Various Qualcomm SoCs do not allow direct access to EFI variables.
71 operations to allow the kernel accessing EFI variables, and via that also
72 provide user-space with access to EFI variables via efivarfs.
74 Select Y here to provide access to EFI variables on the aforementioned
|
| /linux-6.12.1/security/ |
| D | Kconfig.hardening | 13 such variables, depending on the chosen level of coverage.
38 prompt "Initialize kernel stack variables at function entry"
44 This option enables initialization of stack variables at
47 variables initialized), but the performance impact depends
52 uninitialized variables. The selected class of variable will be
89 As a side-effect, this keeps a lot of variables on the
101 Zero-initialize any stack variables that may be passed
107 As a side-effect, this keeps a lot of variables on the
120 information exposures, even variables that were warned about
139 information exposures, even variables that were warned
[all …]
|
| /linux-6.12.1/include/linux/ |
| D | percpu-defs.h | 12 * variables, and definitions of percpu accessors and operations. It
57 * s390 and alpha modules require percpu variables to be defined as
63 * defining percpu variables.
66 * 2. Static percpu variables cannot be defined inside a function.
84 * variables to share the same address, can be detected during build.
109 * ordinary per-CPU variables.
118 * Declaration/definition used for per-CPU variables that must come first in
119 * the set of variables.
128 * Declaration/definition used for per-CPU variables that must be cacheline
155 * Declaration/definition used for per-CPU variables that must be page aligned.
[all …]
|
| D | ccp.h | 160 * Variables required to be set when calling ccp_enqueue_cmd():
225 * Variables required to be set when calling ccp_enqueue_cmd():
278 * Variables required to be set when calling ccp_enqueue_cmd():
335 * Variables required to be set when calling ccp_enqueue_cmd():
369 * Variables required to be set when calling ccp_enqueue_cmd():
429 * Variables required to be set when calling ccp_enqueue_cmd():
458 * Variables required to be set when calling ccp_enqueue_cmd():
571 * Variables required to be set when calling ccp_enqueue_cmd():
632 * Variables required to be set when calling ccp_enqueue_cmd():
638 /* The list_head, work_struct, ccp and ret variables are for use
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/drivers/firmware/efi/ |
| D | mokvar-table.c | 13 * EFI volatile variables by which an EFI boot loader can pass the
16 * EFI MOK variables are present, the table should be considered as
29 * /sys/firmware/efi/mok-variables/
65 * Each /sys/firmware/efi/mok-variables/ sysfs file is represented by
85 * as an alternative to ordinary EFI variables, due to platform-dependent
290 * and create the sysfs entries in /sys/firmware/efi/mok-variables/
328 mokvar_kobj = kobject_create_and_add("mok-variables", efi_kobj); in efi_mokvar_sysfs_init()
330 pr_err("Failed to create EFI mok-variables sysfs entry\n"); in efi_mokvar_sysfs_init()
357 pr_err("Failed to create some EFI mok-variables sysfs entries\n"); in efi_mokvar_sysfs_init()
|
| /linux-6.12.1/arch/alpha/include/asm/ |
| D | percpu.h | 6 * To calculate addresses of locally defined variables, GCC uses
8 * variables in modules, as an offset to the kernel per cpu area is
11 * Always use weak definitions for percpu variables in modules.
|
| /linux-6.12.1/tools/usb/usbip/ |
| D | INSTALL | 19 various system-dependent variables used during compilation. It uses
78 details on some of the pertinent environment variables.
81 by setting variables in the command line or in the environment. Here
86 *Note Defining Variables::, for more details.
176 values for variables like `CC', `cache_file', and `prefix'.
182 Defining Variables
185 Variables not defined in a site shell script can be set in the
188 variables may be lost. In order to avoid this problem, you should set
|
| /linux-6.12.1/drivers/nvmem/layouts/ |
| D | Kconfig | 30 tristate "U-Boot environment variables layout"
34 U-Boot stores its setup as environment variables. This driver adds
35 support for verifying & exporting such data. It also exposes variables
|
| /linux-6.12.1/scripts/kconfig/ |
| D | preprocess.c | 36 * Environment variables
84 * We need to remember all referenced environment variables. in env_expand()
231 * Variables (and user-defined functions)
292 /* For defined variables, += inherits the existing flavor */ in variable_add()
300 /* For undefined variables, += assumes the recursive flavor */ in variable_add()
364 * available, then look-up global-scope variables. in eval_clause()
420 /* Search for variables */ in eval_clause()
468 * Neither single-letter variables as in $A nor curly braces as in ${CC} in expand_dollar_with_args()
552 * Expand variables and functions in the given string. Undefined variables
572 * Expand variables in a token. The parsing stops when a token separater
|
| /linux-6.12.1/tools/memory-model/Documentation/ |
| D | README | 20 Here, "low level" means atomic operations to single variables.
26 o You would like to access lock-protected shared variables without
37 variables so that intentional "racy" accesses can be properly
87 Rules for accessing lock-protected shared variables outside of
|
| /linux-6.12.1/arch/powerpc/include/asm/ |
| D | ps3.h | 67 * struct ps3_dma_region - A per device dma state variables structure
82 /* device variables */
91 /* driver variables (set by ps3_dma_region_create) */
112 * struct ps3_dma_region_init - Helper to initialize structure variables
114 * Helper to properly initialize variables prior to calling
140 * struct ps3_mmio_region - a per device mmio state variables structure
159 * struct ps3_mmio_region_init - Helper to initialize structure variables
161 * Helper to properly initialize variables prior to calling
368 void *driver_priv; /* private driver variables */
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/drivers/net/ethernet/intel/e1000/ |
| D | e1000_hw.c | 90 * @hw: Struct containing variables accessed by shared code
129 * @hw: Struct containing variables accessed by shared code
223 * @hw: Struct containing variables accessed by shared code
331 * @hw: Struct containing variables accessed by shared code
372 * @hw: Struct containing variables accessed by shared code
517 * @hw: Struct containing variables accessed by shared code
641 * @hw: Struct containing variables accessed by shared code.
678 * @hw: Struct containing variables accessed by shared code
793 * @hw: Struct containing variables accessed by shared code
937 * @hw: Struct containing variables accessed by shared code
[all …]
|
| /linux-6.12.1/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::
|