Searched refs:behavior (Results 1 – 14 of 14) sorted by relevance
| /tools/perf/trace/beauty/ |
| D | mmap.c | 82 static size_t madvise__scnprintf_behavior(int behavior, char *bf, size_t size) in madvise__scnprintf_behavior() argument
87 …if (behavior < strarray__madvise_advices.nr_entries && strarray__madvise_advices.entries[behavior]… in madvise__scnprintf_behavior()
88 return scnprintf(bf, size, "MADV_%s", strarray__madvise_advices.entries[behavior]); in madvise__scnprintf_behavior()
90 return scnprintf(bf, size, "%#", behavior); in madvise__scnprintf_behavior()
|
| /tools/kvm/kvm_stat/ |
| D | kvm_stat.txt | 18 This tool is useful for observing guest behavior from the host perspective.
19 Often conclusions about performance or buggy behavior can be drawn from the
|
| /tools/testing/selftests/futex/ |
| D | README | 6 Functional tests shall test the documented behavior of the futex operation
7 code under test. This includes checking for proper behavior under normal use,
|
| /tools/testing/selftests/livepatch/ |
| D | README | 8 livepatch behavior. Debug information is logged to the kernel's message
|
| /tools/perf/Documentation/ |
| D | Build.txt | 66 UndefinedBehaviorSanitizer (or UBSan) is a fast undefined behavior detector
|
| D | perf-timechart.txt | 6 perf-timechart - Tool to visualize total system behavior during a workload
|
| D | perf-kvm.txt | 28 default behavior of perf kvm as --guest, so if neither --host nor --guest
|
| D | perf-top.txt | 212 readability. 0 means no limit (default behavior).
|
| D | perf-stat.txt | 304 in a single row. This option disables that behavior and shows
|
| D | perf-report.txt | 207 readability. 0 means no limit (default behavior).
|
| /tools/lib/traceevent/Documentation/ |
| D | libtraceevent-event_list.txt | 40 It has the same behavior, but the returned array is allocated internally and
|
| /tools/power/pm-graph/ |
| D | README | 87 v3.0 behavior. These patches allow the tool to read all the
89 this behavior on earlier kernels with these patches:
|
| /tools/arch/x86/lib/ |
| D | x86-opcode-map.txt | 281 # Note: "forced64" is Intel CPU behavior: they ignore 0x66 prefix
475 # Note: "forced64" is Intel CPU behavior (see comment about CALL insn).
929 # Note: "forced64" is Intel CPU behavior (see comment about CALL insn).
|
| /tools/memory-model/Documentation/ |
| D | explanation.txt | 92 permissive, in the sense that any behavior allowed by one of these
348 architectural memory models which describe the behavior of machine
763 have a partitioned design that results in non-FIFO behavior. We will
|