| /kernel/linux/linux-5.10/include/linux/ |
| D | percpu-defs.h | 316 #define __pcpu_size_call_return(stem, variable) \ argument
318 typeof(variable) pscr_ret__; \
319 __verify_pcpu_ptr(&(variable)); \
320 switch(sizeof(variable)) { \
321 case 1: pscr_ret__ = stem##1(variable); break; \
322 case 2: pscr_ret__ = stem##2(variable); break; \
323 case 4: pscr_ret__ = stem##4(variable); break; \
324 case 8: pscr_ret__ = stem##8(variable); break; \
331 #define __pcpu_size_call_return2(stem, variable, ...) \ argument
333 typeof(variable) pscr2_ret__; \
[all …]
|
| D | ieee80211.h | 1079 u8 variable[0]; member
1086 u8 variable[0]; member
1104 u8 variable[0]; member
1113 u8 variable[0]; member
1120 u8 variable[0]; member
1125 u8 variable[0]; member
1132 u8 variable[0]; member
1143 u8 variable[0]; member
1147 u8 variable[0]; member
1155 u8 variable[0]; member
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-secvar | 18 This determines the format of the variable and the accepted
19 format of variable updates.
21 What: /sys/firmware/secvar/vars/<variable name>
24 Description: Each secure variable is represented as a directory named as
25 <variable_name>. The variable name is unique and is in ASCII
33 variable. In other words, it represents the size of the data.
38 Description: A read-only file containing the value of the variable. The size
39 of the file represents the maximum size of the variable data.
45 variable. The size of the file represents the maximum size of
46 the variable data that can be written.
|
| /kernel/linux/linux-5.10/scripts/kconfig/tests/preprocess/variable/ |
| D | Kconfig | 6 # Simply expanded variable.
12 # Recursively expanded variable.
18 # Append something to a simply expanded variable.
24 # Append something to a recursively expanded variable.
30 # Use += operator to an undefined variable.
31 # This works as a recursively expanded variable.
37 # You can use variable references for the lefthand side of assignment statement.
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 22 EFI variable flags. Potential values
35 to attain the value of the EFI variable
37 guid: The vendor GUID of the variable. This
39 variable's name.
43 there is to know about the variable.
48 order to update the value of a variable.
62 the variable's value.
73 new variable.
77 variable that has a matching vendor GUID
78 and variable key name.
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intersil/hostap/ |
| D | hostap_80211.h | 22 u8 variable[0]; member
31 u8 variable[0]; member
38 u8 variable[0]; member
45 u8 variable[0]; member
58 u8 variable[0]; member
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/scripts/coccinelle/misc/ |
| D | boolinit.cocci | 159 cocci.print_main("WARNING: Comparison of 0/1 to bool variable",p)
165 cocci.print_main("WARNING: Assignment of 0/1 to bool variable",p1)
171 cocci.print_main("ERROR: Assignment of non-0/1 constant to bool variable",p2)
183 coccilib.report.print_report(p[0],"WARNING: Comparison of 0/1 to bool variable")
189 coccilib.report.print_report(p1[0],"WARNING: Assignment of 0/1 to bool variable")
195 coccilib.report.print_report(p2[0],"ERROR: Assignment of non-0/1 constant to bool variable")
|
| D | ifaddr.cocci | 2 /// The address of a variable or field is likely always to be non-zero.
28 cocci.print_main("test of a variable/field address",p)
34 msg = "ERROR: test of a variable/field address"
|
| D | uninitialized_var.cocci | 8 /// compiler warnings (e.g. "unused variable"). If the compiler thinks it
9 /// is uninitialized, either simply initialize the variable or make compiler
12 /// sure there are no needless variable writes.
|
| D | returnvar.cocci | 3 /// Remove unneeded variable used to store return value.
58 coccilib.report.print_report(p1[0], "Unneeded variable: \"" + ret + "\". Return \"" + C + "\" on li…
66 cocci.print_main("unneeded \"" + ret + "\" variable", p1)
|
| /kernel/linux/linux-5.10/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::
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/scripts/kconfig/ |
| D | preprocess.c | 231 struct variable { struct
239 static struct variable *variable_lookup(const char *name) in variable_lookup() argument
241 struct variable *v; in variable_lookup()
253 struct variable *v; in variable_expand()
282 struct variable *v; in variable_add()
324 static void variable_del(struct variable *v) in variable_del()
334 struct variable *v, *tmp; in variable_all_del()
|
| /kernel/linux/linux-5.10/security/ |
| D | Kconfig.hardening | 8 stack variable initializations, this warning is silenced for
48 Disable automatic stack variable initialization.
50 classes of uninitialized stack variable exploits
60 uninitialized stack variable exploits and information
73 of uninitialized stack variable exploits and information
91 of uninitialized stack variable exploits and information
100 of uninitialized stack variable exploits and information
114 of uninitialized stack variable exploits and information
130 structleak plugin finds a variable it thinks needs to be
143 potential for uninitialized stack variable exploits or information
[all …]
|
| /kernel/linux/linux-5.10/tools/memory-model/litmus-tests/ |
| D | CoWR+poonceonce+Once.litmus | 7 * given variable and a later read from that same variable are ordered.
|
| D | CoRW+poonceonce+Once.litmus | 7 * a given variable and a later write to that same variable are ordered.
|
| /kernel/linux/linux-5.10/fs/efivarfs/ |
| D | Kconfig | 8 variable support via sysfs, as it doesn't suffer from the
9 same 1024-byte variable size limit.
|
| /kernel/linux/linux-5.10/drivers/staging/rtl8723bs/include/ |
| D | rtl8723b_hal.h | 243 void SetHwReg8723B(struct adapter *padapter, u8 variable, u8 *val);
244 void GetHwReg8723B(struct adapter *padapter, u8 variable, u8 *val);
245 u8 SetHalDefVar8723B(struct adapter *padapter, enum HAL_DEF_VARIABLE variable,
247 u8 GetHalDefVar8723B(struct adapter *padapter, enum HAL_DEF_VARIABLE variable,
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-5.10/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 trasmit interrupts, variable 16 receive interrupts
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 108 In order to load SSDTs from an EFI variable the efivar_ssdt kernel command line
109 parameter can be used. The argument for the option is the variable name to
113 In order to store the AML code in an EFI variable the efivarfs filesystem can be
118 EFI variable. Updating a file in /sys/firmware/efi/efivars will update the EFI
119 variable. Please note that the file name needs to be specially formatted as
121 represent the attributes of the EFI variable (see EFI_VARIABLE_MASK in
126 variable with the content from a given file::
|