Searched refs:requires (Results 1 – 25 of 26) sorted by relevance
12
| /tools/testing/selftests/net/forwarding/ |
| D | README | 30 traditional method that requires multiple physical machines, to name a
37 between 4-ports LAGs or 8-way ECMP requires many physical links that are
|
| /tools/testing/selftests/ftrace/ |
| D | ftracetest | 279 requires=`grep "^#[ \t]*requires:" $1 | cut -f2- -d:`
281 eval check_requires "$requires"
|
| /tools/bpf/bpftool/Documentation/ |
| D | bpftool-iter.rst | 43 Map element bpf iterator requires an additional parameter
|
| /tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 44 This module requires these other modules and libraries:
|
| /tools/memory-model/Documentation/ |
| D | README | 1 It has been said that successful communication requires first identifying
|
| D | explanation.txt | 276 In short, if a memory model requires certain accesses to be ordered,
322 describe in the following sections. The memory model requires certain
323 of these relations to be orderings, that is, it requires them not to
551 attempt to do so. It requires all accesses to be properly aligned and
560 memory contents. Specifically, it requires that for each location in
732 For the most part, executing an instruction requires a CPU to perform
846 The operational model requires that whenever W and W' are both stores
863 Sequential consistency per variable: This requires that the
866 Atomicity: This requires that atomic read-modify-write
870 Happens-before: This requires that certain instructions are
[all …]
|
| D | glossary.txt | 134 data between two CPUs requires that both CPUs their accesses.
|
| D | recipes.txt | 477 first. Preserving order requires nothing less than full barriers:
|
| D | access-marking.txt | 135 Note that this use case requires that the heuristic be able to handle
|
| D | ordering.txt | 514 C-language accesses requires careful attention to not just your code,
|
| /tools/perf/Documentation/ |
| D | perf-buildid-cache.txt | 33 /proc/kcore which requires root permissions to read. Be aware that
|
| D | perf-annotate.txt | 91 --tui:: Use the TUI interface. Use of --tui requires a tty, if one is not
|
| D | perf-report.txt | 206 function and searched through the callchain, thus it requires callchain
277 and will be sorted on the data. It requires callchains are recorded.
314 requires a tty, if one is not present, as when piping to other
443 requires the argument to be quoted e.g. --time "1234.567,1234.789 1235,"
|
| D | perf-top.txt | 190 and will be sorted on the data. It requires -g/--call-graph option
245 The option requires at least one branch type among any, any_call, any_ret, ind_call, cond.
|
| D | perf-script.txt | 244 sampling periods, similar to perf stat. This requires
389 requires the argument to be quoted e.g. --time "1234.567,1234.789 1235,"
|
| D | perf-diff.txt | 155 Multiple ranges can be separated by spaces, which requires the argument
|
| D | jitdump-specification.txt | 27 The format requires only sequential accesses, i.e., append only mode. The file starts with a fixed …
|
| D | perf-list.txt | 132 to PMUs. Using this typically requires looking up the specific event
|
| D | perf-intel-pt.txt | 120 Dump all instructions. This requires installing the xed tool (see XED below)
764 which in turn requires CAP_PERFMON or CAP_SYS_ADMIN.
1138 Below is an example of using Intel PT with autofdo. It requires autofdo
1193 using 'perf inject' and requires unchanging VMX TSC Offset and no VMX TSC Scaling.
|
| D | perf-record.txt | 67 - 'aux-output': Generate AUX records instead of events. This requires
390 The option requires at least one branch type among any, any_call, any_ret, ind_call, cond.
|
| D | perf-probe.txt | 302 …- Since tracefs and kallsyms requires root or privileged user to access it, the following perf pro…
|
| /tools/lib/perf/Documentation/ |
| D | libperf-counting.txt | 26 It requires root access, because of the `PERF_COUNT_SW_CPU_CLOCK` event,
|
| D | libperf-sampling.txt | 34 It requires root access, because it uses hardware cycles event.
|
| /tools/testing/selftests/tc-testing/ |
| D | README | 181 necessary if a test case being run requires a specific plugin to work.
|
| /tools/arch/x86/lib/ |
| D | x86-opcode-map.txt | 25 # (ev): this opcode requires EVEX prefix.
27 # (v): this opcode requires VEX prefix.
|
12