/tools/power/acpi/os_specific/service_layers/ |
D | osunixmap.c | 63 void *acpi_os_map_memory(acpi_physical_address where, acpi_size length) in acpi_os_map_memory() argument 79 offset = where % page_size; in acpi_os_map_memory() 84 fd, (where - offset)); in acpi_os_map_memory() 109 void acpi_os_unmap_memory(void *where, acpi_size length) in acpi_os_unmap_memory() argument 115 offset = ACPI_TO_INTEGER(where) % page_size; in acpi_os_unmap_memory() 116 munmap((u8 *)where - offset, (length + offset)); in acpi_os_unmap_memory()
|
D | osunixxf.c | 491 void *acpi_os_map_memory(acpi_physical_address where, acpi_size length) in acpi_os_map_memory() argument 494 return (ACPI_TO_POINTER((acpi_size)where)); in acpi_os_map_memory() 511 void acpi_os_unmap_memory(void *where, acpi_size length) in acpi_os_unmap_memory() argument
|
/tools/lib/traceevent/Documentation/ |
D | libtraceevent-long_size.txt | 7 the machine, where the trace is generated, in bytes 22 where the trace is generated. The _tep_ argument is trace event parser context. 25 where the trace is generated. The _tep_ argument is trace event parser context. 31 where the trace is generated, in bytes.
|
D | libtraceevent-page_size.txt | 7 the machine, where the trace is generated 22 the machine, where the trace is generated. The _tep_ argument is trace 26 memory page on the machine, where the trace is generated.
|
D | libtraceevent-parse_event.txt | 23 _tep_ context. The _buf_ argument is a buffer with _size_, where the event 29 difference is in the extra _eventp_ argument, where the newly created event
|
D | libtraceevent-endian_read.txt | 21 is the trace event parser context. The _ptr_ is a pointer to the raw data, where
|
/tools/perf/Documentation/ |
D | itrace.txt | 17 except for perf script where it is --itrace=ce 19 In addition, the period (default 100000, except for perf script where it is 1)
|
D | perf-inject.txt | 40 Merge sched_stat and sched_switch for getting events where and how long 41 tasks slept. sched_switch contains a callchain where a task slept and
|
/tools/memory-model/litmus-tests/ |
D | LB+poacquireonce+pooncerelease.litmus | 7 * test, where each process reads from one of two variables then writes
|
D | SB+poonceonces.litmus | 7 * to order the store-buffering pattern, where each process writes to the
|
D | SB+fencembonceonces.litmus | 7 * order the store-buffering pattern, where each process writes to the
|
D | WRC+poonceonces+Once.litmus | 7 * where the first write is moved to a separate process. Note that this
|
D | WRC+pooncerelease+fencermbonceonce+Once.litmus | 6 * This litmus test is an extension of the message-passing pattern, where
|
D | IRIW+poonceonces+OnceOnce.litmus | 9 * of a pair of writes, where each write is to a different variable by a
|
D | IRIW+fencembonceonces+OnceOnce.litmus | 9 * of writes, where each write is to a different variable by a different
|
D | README | 27 the order of a pair of writes, where each write is to a different 35 order of a pair of writes, where each write is to a different 54 load-buffering litmus test, where each process reads from one 59 litmus test, where each process reads from one of two variables then 95 the loads) suffice for the message-passing litmus test, where one
|
/tools/perf/pmu-events/arch/nds32/ |
D | mapfile.csv | 4 # where
|
/tools/perf/pmu-events/arch/powerpc/ |
D | mapfile.csv | 4 # where
|
/tools/perf/pmu-events/ |
D | README | 27 should be placed in a separate JSON file - where the file name identifies 39 for instances where the arch and vendor are not the same. 95 where 'pm_1plus_ppc_cmpl' is a Power8 PMU event. 110 where:
|
/tools/perf/pmu-events/arch/arm64/ |
D | mapfile.csv | 4 # where
|
/tools/bpf/ |
D | bpf_dbg.c | 536 static void bpf_set_breakpoints(unsigned int where) in bpf_set_breakpoints() argument 542 if (bpf_breakpoints[i] == (int) where) { in bpf_set_breakpoints() 549 bpf_breakpoints[i] = where; in bpf_set_breakpoints() 1164 unsigned int where = strtoul(subcmd, NULL, 10); in cmd_breakpoint() local 1166 if (where < bpf_prog_len) { in cmd_breakpoint() 1167 bpf_set_breakpoints(where); in cmd_breakpoint() 1169 bpf_disasm(bpf_image[where], where); in cmd_breakpoint()
|
/tools/testing/ktest/examples/ |
D | README | 28 are included by other config files, where the other config files define
|
/tools/memory-model/Documentation/ |
D | explanation.txt | 140 This pattern of memory accesses, where one CPU stores values to two 172 However, the most interesting possibility is where r1 = 1 and r2 = 0. 307 write event is omitted for executions where it doesn't occur, such as 308 a cmpxchg() where the comparison fails.) 317 index, the address where the value gets stored), but the memory model 483 R ->addr X, or R ->ctrl X (where R is a read event), then we must also 496 further distinguish the cases where the load and the store occur on 497 the same CPU (internal reads-from, or rfi) and where they occur on 506 of load-tearing, where a load obtains some of its bits from one store 584 W' in program order and they access the same location), where W [all …]
|
/tools/build/Documentation/ |
D | Build.txt | 10 Unlike the kernel we don't have a single build object 'obj-y' list that where 29 where:
|
/tools/usb/usbip/ |
D | INSTALL | 94 directory where you want the object files and executables to go and run 130 `configure', where FEATURE indicates an optional part of the package. 131 They may also pay attention to `--with-PACKAGE' options, where PACKAGE 154 where SYSTEM can have one of these forms:
|