| /linux-3.3/include/linux/ |
| D | percpu-defs.h | 32 * s390 and alpha modules require percpu variables to be defined as
38 * defining percpu variables.
41 * 2. Static percpu variables cannot be defined inside a function.
59 * variables to share the same address, can be detected during build.
85 * ordinary per-CPU variables.
94 * Declaration/definition used for per-CPU variables that must come first in
95 * the set of variables.
104 * Declaration/definition used for per-CPU variables that must be cacheline
131 * Declaration/definition used for per-CPU variables that must be page aligned.
142 * Declaration/definition used for per-CPU variables that must be read mostly.
[all …]
|
| D | ktime.h | 90 /* Subtract two ktime_t variables. rem = lhs -rhs: */
94 /* Add two ktime_t variables. res = lhs + rhs: */
157 * ktime_sub - subtract two ktime_t variables
175 * ktime_add - add two ktime_t variables
281 * ktime_equal - Compares two ktime_t variables to see if they are equal
285 * Compare two ktime_t variables, returns 1 if equal
|
| D | seqlock.h | 22 * to increment the sequence variables because an interrupt routine could
133 * provided before actually loading any of the variables that are to be
176 * provided before actually loading any of the variables that are to be
|
| /linux-3.3/include/xen/interface/ |
| D | platform.h | 40 /* IN variables. */
56 /* IN variables. */
60 /* OUT variables. */
75 /* IN variables. */
84 /* IN variables. */
86 /* OUT variables. */
95 /* IN variables. */
106 /* IN variables. */
116 /* IN variables. */
119 /* OUT variables. */
[all …]
|
| /linux-3.3/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
31 explanation of each of these variables.
66 removing variables:
|
| /linux-3.3/drivers/net/fddi/skfp/h/ |
| D | sba.h | 36 * Node variables
57 * Session variables
85 * variables for allocation actions
106 * SBA variables
112 * SBA state machine variables
122 * variables for the End Station Support
137 * variables for the ess bandwidth control
|
| /linux-3.3/Documentation/ |
| D | local_ops.txt | 9 those local variables across CPUs when the order of memory writes matters.
50 - Variables touched by local ops must be per cpu variables.
51 - _Only_ the CPU owner of these variables must write to them.
53 to update its local_t variables.
65 - Reads of these variables can be done from any CPU, because updates to
66 "long", aligned, variables are always atomic. Since no memory
68 variable can be read when reading some _other_ cpu's variables.
|
| D | ramoops.txt | 18 the memory area are set using two variables:
36 1. Use the module parameters (which have the names of the variables described
|
| /linux-3.3/Documentation/filesystems/ |
| D | gfs2-uevents.txt | 18 The ADD uevent has two environment variables: SPECTATOR=[0|1]
26 has the same environment variables as the ADD uevent. The ONLINE
27 uevent, along with the two environment variables for spectator and
40 two environment variables, JID= which specifies the journal id which
48 without checking the environment variables to discover the state, we
70 Information common to all GFS2 uevents (uevent environment variables)
|
| /linux-3.3/arch/alpha/include/asm/ |
| D | percpu.h | 5 * To calculate addresses of locally defined variables, GCC uses
7 * variables in modules, as an offset to the kernel per cpu area is
10 * Always use weak definitions for percpu variables in modules.
|
| /linux-3.3/drivers/staging/usbip/userspace/ |
| 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-3.3/tools/perf/Documentation/ |
| D | perf-probe.txt | 27 and C local variables) with debuginfo.
71 Show available local variables at given probe point. The argument
75 (Only for --vars) Show external defined variables in addition to local
76 variables.
154 The filter pattern is a glob matching pattern(s) to filter variables.
158 With --filter "foo* | bar*", perf probe -V shows variables which start with "foo" or "bar".
159 …With --filter "!foo* & *bar", perf probe -V shows variables which don't start with "foo" and end w…
|
| /linux-3.3/drivers/net/ethernet/intel/ixgb/ |
| D | ixgb_ee.c | 48 * hw - Struct containing variables accessed by shared code
67 * hw - Struct containing variables accessed by shared code
86 * hw - Struct containing variables accessed by shared code
136 * hw - Struct containing variables accessed by shared code
176 * hw - Struct containing variables accessed by shared code
200 * hw - Struct containing variables accessed by shared code
237 * hw - Struct containing variables accessed by shared code
262 * hw - Struct containing variables accessed by shared code
281 * hw - Struct containing variables accessed by shared code
319 * hw - Struct containing variables accessed by shared code
[all …]
|
| D | ixgb_hw.c | 119 * hw - Struct containing variables accessed by shared code
180 * hw - Struct containing variables accessed by shared code.
219 * hw - Struct containing variables accessed by shared code. The device_id
283 * hw - Struct containing variables accessed by shared code
376 * hw - Struct containing variables accessed by shared code
422 * hw - Struct containing variables accessed by shared code
490 * hw - Struct containing variables accessed by shared code
541 * hw - Struct containing variables accessed by shared code
572 * hw - Struct containing variables accessed by shared code
604 * hw - Struct containing variables accessed by shared code
[all …]
|
| /linux-3.3/arch/powerpc/include/asm/ |
| D | ps3.h | 80 * struct ps3_dma_region - A per device dma state variables structure
94 /* device variables */
102 /* driver variables (set by ps3_dma_region_create) */
123 * struct ps3_dma_region_init - Helper to initialize structure variables
125 * Helper to properly initialize variables prior to calling
151 * struct ps3_mmio_region - a per device mmio state variables structure
170 * struct ps3_mmio_region_init - Helper to initialize structure variables
172 * Helper to properly initialize variables prior to calling
379 void *driver_priv; /* private driver variables */
|
| /linux-3.3/drivers/net/ethernet/intel/e1000/ |
| D | e1000_hw.c | 113 * @hw: Struct containing variables accessed by shared code
154 * @hw: Struct containing variables accessed by shared code
250 * @hw: Struct containing variables accessed by shared code
360 * @hw: Struct containing variables accessed by shared code
403 * @hw: Struct containing variables accessed by shared code
550 * @hw: Struct containing variables accessed by shared code
672 * @hw: Struct containing variables accessed by shared code.
712 * @hw: Struct containing variables accessed by shared code
828 * @hw: Struct containing variables accessed by shared code
970 * @hw: Struct containing variables accessed by shared code
[all …]
|
| /linux-3.3/drivers/net/ethernet/atheros/atl1e/ |
| D | atl1e_hw.c | 149 * hw - Struct containing variables accessed by shared code
182 * hw - Struct containing variables accessed by shared code
210 * hw - Struct containing variables accessed by shared code
243 * hw - Struct containing variables accessed by shared code
294 * hw - Struct containing variables accessed by shared code
383 * hw - Struct containing variables accessed by shared code
512 * hw - Struct containing variables accessed by shared code
567 * hw - Struct containing variables accessed by shared code
592 * hw - Struct containing variables accessed by shared code
|
| /linux-3.3/drivers/staging/olpc_dcon/ |
| D | TODO | 7 - drop global variables, use a proper olpc_dcon_priv struct
9 workarounds, ancient variables (noaa?), etc
|
| /linux-3.3/arch/arm/boot/compressed/ |
| D | misc.c | 12 * For this code to run directly from Flash, all constant variables must
13 * be marked with 'const' and all other variables initialized at run-time
14 * only. This way all non constant variables will end up in the bss segment,
|
| /linux-3.3/arch/frv/include/asm/ |
| D | sections.h | 1 /* sections.h: linkage layout variables
23 * we don't want to put variables in the GP-REL section if they're not used very much - that would
|
| /linux-3.3/tools/testing/ktest/ |
| D | sample.conf | 94 # integer, and can use the config variables (explained below).
173 # statements. Config variables will be passed to these files and changes
174 # to config variables will be seen by top level config files. Including
198 #### Config variables ####
200 # This config file can also contain "config variables".
204 # The difference between ktest options and config variables
205 # is that config variables can be used multiple times,
209 # The advantage to config variables are that they can be used
210 # by any option or any other config variables to define thing
242 # Note, the config variables are evaluated immediately, thus
[all …]
|
| /linux-3.3/arch/x86/include/asm/ |
| D | vvar.h | 6 * A handful of variables are accessible (read-only) from userspace
13 * These variables live in a page of kernel data that has an extra RO
|
| /linux-3.3/arch/mips/pmc-sierra/msp71xx/ |
| D | msp_prom.c | 53 /* global PROM environment variables and pointers */
289 * points to a null terminated array of pointers to variables. in prom_getenv()
290 * Environment variables are stored in the form of "memsize=64" in prom_getenv()
369 * preserve environment variables and command line from pmon/bbload in prom_free_prom_memory()
389 /* next preserve the environment variables */ in prom_free_prom_memory()
393 i++; /* count number of environment variables */ in prom_free_prom_memory()
|
| /linux-3.3/arch/alpha/boot/ |
| D | misc.c | 12 * For this code to run directly from Flash, all constant variables must
13 * be marked with 'const' and all other variables initialized at run-time
14 * only. This way all non constant variables will end up in the bss segment,
|
| /linux-3.3/drivers/misc/sgi-xp/ |
| D | xpc_sn2.c | 34 * Memory for XPC's amo variables is allocated by the MSPEC driver. These
40 * amo variables (based on XP_MAX_NPARTITIONS_SN2) to identify the senders of
41 * NOTIFY IRQs, 128 amo variables (based on XP_NASID_MASK_WORDS_SN2) to identify
694 /* initialize the activate IRQ related amo variables */ in xpc_setup_rsvd_page_sn2()
698 /* initialize the engaged remote partitions related amo variables */ in xpc_setup_rsvd_page_sn2()
801 * Get a copy of the remote partition's XPC variables from the reserved page.
815 /* pull over the cross partition variables */ in xpc_get_remote_vars_sn2()
1018 /* pull over the cross partition variables */ in xpc_identify_activate_IRQ_req_sn2()
1024 dev_warn(xpc_part, "unable to get XPC variables from nasid %d, " in xpc_identify_activate_IRQ_req_sn2()
1087 * Loop through the activation amo variables and process any bits
[all …]
|