Searched refs:internal (Results 1 – 16 of 16) sorted by relevance
| /tools/testing/selftests/kvm/x86_64/ |
| D | vmx_apic_access_test.c | 113 TEST_ASSERT(run->internal.suberror == in main()
116 run->internal.suberror); in main()
|
| D | mmio_warning_test.c | 48 res, run->exit_reason, run->internal.suberror); in thr()
|
| /tools/testing/selftests/firmware/ |
| D | settings | 5 # Additionally, fw_fallback may take 5 seconds for internal timeouts in each
|
| /tools/power/pm-graph/config/ |
| D | custom-timeline-functions.cfg | 61 # Do not use the internal default functions for timeline entries (default: false)
66 # Do not use the internal default functions for dev timeline entries (default: false)
73 # The tool has an internal set of these functions which should cover the
|
| D | example.cfg | 110 # Do not use the internal default functions for timeline entries (def: false)
115 # Do not use the internal default functions for dev timeline entries (def: false)
|
| /tools/power/pm-graph/ |
| D | README | 324 Sample for editing timeline funcs (moves internal functions into config)
407 # Do not use the internal default functions for timeline entries (def: false)
412 # Do not use the internal default functions for dev timeline entries (def: false)
438 the config. It's also possible to copy the internal timeline functions into
444 custom calls, or leave it false to append them to the internal ones.
453 all the internal timeline functions into the config and allows you to edit
512 to the config. It's also possible to copy the internal dev timeline
518 custom calls, or leave it false to append them to the internal ones.
528 all the internal dev timeline functions into the config and allows you to edit
546 custom and internal if you haven't overridden them) and actually attempts
|
| /tools/memory-model/Documentation/ |
| D | glossary.txt | 48 is a "coherence internal" (coi) link. The term "coherence
111 is a "from-reads internal" (fri) link. The term "from-reads
152 is a "reads-from internal" (rfi) link. The term "reads-from
|
| D | explanation.txt | 497 the same CPU (internal reads-from, or rfi) and where they occur on
673 occur on the same CPU (internal coherence order, or coi) and stores
733 only internal operations. However, loads, stores, and fences involve
|
| /tools/perf/Documentation/ |
| D | perf-bench.txt | 68 Benchmark internal perf functionality.
|
| D | perf-dlfilter.txt | 62 internal filtering.
|
| D | perf-config.txt | 508 This option sets up the maximum allocation size of the internal
|
| /tools/lib/traceevent/Documentation/ |
| D | libtraceevent-reg_print_func.txt | 64 Some events have internal functions calls, that appear in the print format
|
| D | libtraceevent-func_apis.txt | 70 it was stored in the kernel. Some strings internal to the kernel with static
|
| /tools/memory-model/litmus-tests/ |
| D | README | 209 reads-from link (rf) and internal to the P0() process. This is
210 "rfi", which is an abbreviation for "reads-from internal". Because
|
| /tools/memory-model/ |
| D | README | 190 Maps from C-like syntax to herd7's internal litmus-test
|
| /tools/include/uapi/linux/ |
| D | kvm.h | 388 } internal; member
|