Searched full:variables (Results 1 – 25 of 2539) sorted by relevance
12345678910>>...102
| /kernel/linux/linux-6.6/drivers/gpu/drm/ci/ |
| D | test.yml | 24 variables:
39 variables:
54 variables:
71 variables:
90 variables:
103 variables:
122 variables:
136 variables:
148 variables:
162 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:
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/include/xen/interface/ |
| D | platform.h | 40 /* IN variables. */
48 /* IN variables. */
65 /* IN variables. */
69 /* OUT variables. */
84 /* IN variables. */
93 /* IN variables. */
95 /* OUT variables. */
104 /* IN variables. */
115 /* IN variables. */
228 /* IN variables. */
[all …]
|
| /kernel/linux/linux-6.6/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)
|
| /kernel/linux/linux-5.10/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)
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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
170 shadow variables to parents already in-flight.
208 Shadow variables can also be used as a flag indicating that a data
[all …]
|
| /kernel/linux/linux-5.10/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
87 As a side-effect, this keeps a lot of variables on the
98 Zero-initialize any stack variables that may be passed
104 As a side-effect, this keeps a lot of variables on the
116 information exposures, even variables that were warned about
134 information exposures, even variables that were warned
[all …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 6 EFI variables. For more information on EFI variables,
10 In summary, EFI variables are named, and are classified
15 The efivars module enumerates these variables and
32 explanation of each of these variables.
68 removing variables:
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 6 EFI variables. For more information on EFI variables,
10 In summary, EFI variables are named, and are classified
15 The efivars module enumerates these variables and
32 explanation of each of these variables.
68 removing variables:
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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
274 * and create the sysfs entries in /sys/firmware/efi/mok-variables/
312 mokvar_kobj = kobject_create_and_add("mok-variables", efi_kobj); in efi_mokvar_sysfs_init()
314 pr_err("Failed to create EFI mok-variables sysfs entry\n"); in efi_mokvar_sysfs_init()
341 pr_err("Failed to create some EFI mok-variables sysfs entries\n"); in efi_mokvar_sysfs_init()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
12345678910>>...102