Searched refs:shown (Results 1 – 25 of 31) sorted by relevance
12
/tools/perf/Documentation/ |
D | callchain-overhead-calculation.txt | 3 The overhead can be shown in two columns as 'Children' and 'Self' when 100 So '\_\_libc_start_main' and 'main' are shown first since they have 104 Since v3.16 the 'children' overhead is shown by default and the output
|
D | perf-probe.txt | 207 …shown in hexadecimal format. Traced arguments are shown in decimal (sNN/uNN) or hex (xNN). You can…
|
D | perf-kvm.txt | 31 perf.data.host, please input --host --no-guest. The behaviors are shown as
|
D | perf-script-python.txt | 271 The final script producing the output shown above is shown in its 321 interested in by looking at the list of available events shown by
|
D | perf-diff.txt | 124 sum of shown entries will be always 100%. "absolute" means it retains
|
D | perf-report.txt | 180 field will be shown only for the event has the field. The event name 432 sum of shown entries will be always 100%. "absolute" means it retains
|
D | perf-top.txt | 221 sum of shown entries will be always 100%. "absolute" means it retains
|
D | perf-intel-pt.txt | 619 memory as shown in /proc/self/limits). Note that perf does not count the first 809 The sched_switch events are automatically added. e.g. the second event shown 1383 shown above with the calculated TSC Offset. For an unchanging TSC Offset 1491 And then copy guest-sideband-testing-guest-perf.data to the host (not shown here).
|
D | perf-config.txt | 396 shown, 3 or higher will show offsets for all instructions.
|
/tools/testing/kunit/android/ |
D | README | 94 Check dmesg for load errors. If undefined symbol errors are shown, you're 103 If "kunit: disabled" is shown then `kunit.enable=1` has not been set.
|
/tools/memory-model/Documentation/ |
D | recipes.txt | 217 the desired MP ordering. The general approach is shown below: 248 pointers. The general approach is shown below: 276 (address dependency, as shown above), the value written by a later store 293 to understand their use cases. The general approach is shown below: 381 The A/D pairing from the ring-buffer use case shown earlier also 495 values of 0, but providing both full barriers as shown above prevents
|
D | locking.txt | 116 as shown in this corrected version: 230 initial value and the second to return the updated value, as shown below:
|
D | litmus-tests.txt | 17 useful is shown near the beginning. 133 "r" followed by a number as shown here. A common bug in litmus tests 212 Another important part of this output is shown in lines 2-5, repeated here: 1000 operations, as shown in the linux-kernel.def file. 1018 c. The call_rcu() function is not modeled. As was shown above,
|
D | control-dependencies.txt | 231 because, as shown by the example above, optimizing compilers can
|
D | simple.txt | 163 foo_get_a() shown in Documentation/RCU/whatisRCU.rst. Additional
|
D | access-marking.txt | 28 These may be used in combination, as shown in this admittedly improbable
|
D | ordering.txt | 157 o smp_mb__after_atomic(), which, as shown above, provides full
|
/tools/testing/selftests/rcutorture/bin/ |
D | kvm-test-1-run.sh | 176 echo " 1." Set your bare-metal build tree to the state shown in this file: >> $resdir/bare-metal
|
/tools/bpf/bpftool/Documentation/ |
D | bpftool-map.rst | 66 *MAP* may match several maps which will all be shown.
|
D | bpftool-prog.rst | 73 programs which will all be shown.
|
/tools/usb/usbip/ |
D | INSTALL | 229 messages will still be shown).
|
/tools/power/x86/turbostat/ |
D | turbostat.c | 223 unsigned int shown; variable 6711 if (shown == 0) in cmdline() 6715 shown = 1; in cmdline()
|
/tools/power/cpupower/po/ |
D | ka.po | 138 msgid " all supported monitors are shown\n"
|
D | fr.po | 125 msgid " all supported monitors are shown\n"
|
D | it.po | 125 msgid " all supported monitors are shown\n"
|
12