| /linux/include/xen/interface/ |
| H A 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/Documentation/livepatch/ |
| H A 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/tools/testing/selftests/net/forwarding/ |
| H A D | README | 78 The forwarding selftests framework uses a number of variables that
80 various ways. A number of these variables can be overridden. The way these
81 overridable variables are specified is typically one of the following two
87 Any of these variables can be overridden. Notably net/forwarding/lib.sh and
88 net/lib.sh contain a number of overridable variables.
90 One way of overriding these variables is through the environment:
100 A way to customize variables in a persistent fashion is to create a file
103 assignments of variables whose value should be overridden.
|
| /linux/Documentation/filesystems/ |
| H A 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
|
| /linux/drivers/net/fddi/skfp/h/ |
| H A 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/drivers/firmware/qcom/ |
| H A 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/Documentation/core-api/ |
| H A 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/drivers/firmware/efi/ |
| H A 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
287 * and create the sysfs entries in /sys/firmware/efi/mok-variables/
325 mokvar_kobj = kobject_create_and_add("mok-variables", efi_kobj); in efi_mokvar_sysfs_init()
327 pr_err("Failed to create EFI mok-variables sysfs entry\n"); in efi_mokvar_sysfs_init()
354 pr_err("Failed to create some EFI mok-variables sysfs entries\n"); in efi_mokvar_sysfs_init()
|
| /linux/scripts/kconfig/ |
| H A 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/tools/usb/usbip/ |
| H A 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/arch/powerpc/include/asm/ |
| H A D | ps3.h | 67 * struct ps3_dma_region - A per device dma state variables structure
83 /* device variables */
92 /* driver variables (set by ps3_dma_region_create) */
116 * struct ps3_dma_region_init - Helper to initialize structure variables
118 * Helper to properly initialize variables prior to calling
141 * struct ps3_mmio_region - a per device mmio state variables structure
160 * ps3_mmio_region_init - Helper to initialize structure variables
162 * Helper to properly initialize variables prior to calling
371 void *driver_priv; /* private driver variables */
|
| /linux/drivers/nvmem/layouts/ |
| H A 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/Documentation/bpf/libbpf/ |
| H A 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/tools/memory-model/Documentation/ |
| H A D | README | 20 Here, "low level" means atomic operations to single variables.
26 o You need to locklessly access shared variables that are otherwise
40 variables so that intentional "racy" accesses can be properly
90 Rules for accessing lock-protected shared variables outside of
|
| /linux/include/linux/ |
| H A 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/Documentation/ABI/testing/ |
| H A D | sysfs-uevent | 6 Enable passing additional variables for synthetic uevents that
37 with existing variables.
43 This generates synthetic uevent including these variables::
|
| /linux/drivers/net/ethernet/atheros/atl1e/ |
| H A D | atl1e_hw.c | 136 * hw - Struct containing variables accessed by shared code
169 * hw - Struct containing variables accessed by shared code
197 * hw - Struct containing variables accessed by shared code
230 * hw - Struct containing variables accessed by shared code
281 * hw - Struct containing variables accessed by shared code
370 * hw - Struct containing variables accessed by shared code
499 * hw - Struct containing variables accessed by shared code
554 * hw - Struct containing variables accessed by shared code
579 * hw - Struct containing variables accessed by shared code
|
| /linux/Documentation/networking/ |
| H A D | seg6-sysctl.rst | 4 Seg6 Sysfs variables
8 /proc/sys/net/conf/<iface>/seg6_* variables:
28 /proc/sys/net/ipv6/seg6_* variables:
|
| /linux/tools/testing/selftests/drivers/net/ |
| H A D | README.rst | 26 Refer to list of :ref:`Variables` later in this file to set up running
40 Variables
43 The variables can be set in the environment or by creating a net.config
59 need only the ``NETIF`` variable. Remaining variables define the endpoint
36 Variables global() chapter
|
| /linux/Documentation/kbuild/ |
| H A D | kconfig.rst | 39 Environment variables
42 Environment variables for ``*config``:
70 Environment variables for ``{allyes/allmod/allno/alldef/rand}config``:
108 Environment variables for ``randconfig``:
147 Environment variables for ``syncconfig``:
255 Environment variables:
|
| H A 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
|
| /linux/kernel/configs/ |
| H A D | hardening.config | 60 # Initialize all heap variables to zero on allocation.
63 # Initialize all heap variables to zero on free to reduce stale data lifetime.
66 # Initialize all stack variables to zero on function entry.
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-probe.txt | 31 and C local variables) with debuginfo.
92 Show available local variables at given probe point. The argument
96 (Only for --vars) Show external defined variables in addition to local
97 variables.
206 '$vars' and '$params' special arguments are also available for NAME, '$vars' is expanded to the local variables (including function parameters) which can access at given probe point. '$params' is expanded to only the function parameters.
244 The filter pattern is a glob matching pattern(s) to filter variables.
248 With --filter "foo* | bar*", perf probe -V shows variables which start with "foo" or "bar".
249 With --filter "!foo* & *bar", perf probe -V shows variables which don't start with "foo" and end with "bar", like "fizzbar". But "foobar" is filtered out.
|
| /linux/samples/livepatch/ |
| H A D | livepatch-shadow-fix2.c | 7 * livepatch-shadow-fix2.c - Shadow variables, livepatch demo
125 /* Cleanup any existing SV_COUNTER shadow variables */ in livepatch_shadow_fix2_exit()
131 MODULE_DESCRIPTION("Live patching demo for shadow variables");
|
| /linux/Documentation/devicetree/bindings/nvmem/layouts/ |
| H A 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.
|