| /tools/perf/ |
| D | builtin-report.c | 70 struct report { struct
112 struct report *rep = cb; in report__config() argument
145 struct report *rep = arg; in hist_iter__report_callback()
188 struct report *rep = arg; in hist_iter__branch_callback()
210 static void setup_forced_leader(struct report *report, in setup_forced_leader() argument
213 if (report->group_set) in setup_forced_leader()
220 struct report *rep = container_of(session->tool, struct report, tool); in process_feature_event()
246 struct report *rep = container_of(tool, struct report, tool); in process_sample_event()
320 struct report *rep = container_of(tool, struct report, tool); in process_read_event()
338 static int report__setup_sample_type(struct report *rep) in report__setup_sample_type()
[all …]
|
| D | Build | 14 perf-y += builtin-report.o
46 CFLAGS_builtin-report.o += -DTIPDIR="BUILD_STR($(tipdir_SQ))"
47 CFLAGS_builtin-report.o += -DDOCDIR="BUILD_STR($(srcdir_SQ)/Documentation)"
|
| D | .gitignore | 11 perf-report
|
| /tools/perf/Documentation/ |
| D | tips.txt | 1 For a higher level overview, try: perf report --sort comm,dso
4 Boolean options have negative forms, e.g.: perf report --no-children
9 Search options using a keyword: perf report -h <keyword>
10 Use parent filter to see specific call path: perf report -p <regex>
14 To see callchains in a more compact form: perf report -g folded
16 Limit to show entries above 5% only: perf report --percent-limit 5
17 Profiling branch (mis)predictions with: perf record -b / perf report
19 Treat branches as callchains: perf report --branch-history
22 If you have debuginfo enabled, try: perf report -s sym,srcline
23 For memory address profiling, try: perf mem record / perf mem report
[all …]
|
| D | perf-mem.txt | 11 'perf mem' [<options>] (record [<command>] | report)
18 "perf mem report" displays the result. It invokes perf report with the
87 In addition, for report all perf report options are valid, and for record
92 linkperf:perf-record[1], linkperf:perf-report[1]
|
| D | perf-kvm.txt | 13 {top|record|report|diff|buildid-list} [<options>]
15 | --guestvmlinux=<path>] {top|record|report|diff|buildid-list|stat} [<options>]
16 'perf kvm stat [record|report|live] [<options>]
39 'perf kvm report' to display the performance counter profile information
47 for use by perf report. As buildid is read from /sys/kernel/notes in os, then
53 Especially, perf 'kvm stat record/report' generates a statistical analysis
60 'perf kvm stat report' reports statistical data which includes events
64 record + report but with statistical data updated live at a given display
71 Input file name, for the 'report', 'diff' and 'buildid-list' subcommands.
74 Output file name, for the 'record' subcommand. Doesn't work with 'report',
[all …]
|
| D | perfconfig.example | 14 report = on
31 [report]
|
| D | perf-buildid-list.txt | 17 perf report.
43 linkperf:perf-report[1]
|
| D | perf-lock.txt | 11 'perf lock' {record|report|script|info}
23 'perf lock report' reports statistical data.
|
| D | perf-config.txt | 89 report = on
119 [report]
139 To modify the sort order of report functionality in user config file(i.e. `~/.perfconfig`), do
141 % perf config --user report sort-order=srcline
154 % perf config report.queue-size call-graph.order report.children
169 'report', 'top' and 'annotate' in the TUI. They should specify the
197 from sub-commands (top, report, annotate).
207 Colors for headers in the output of a sub-commands (top, report).
217 Subcommands that can be configured here are 'top', 'report' and 'annotate'.
409 in 'report' and 'top'. If this option is false, they are hidden.
[all …]
|
| D | perf-c2c.txt | 13 'perf c2c report' [<options>]
31 The c2c tool provide means to record this data and report back access details
34 The basic workflow with this tool follows the standard record/report phase.
35 User uses the record command to record events data and report command to
78 Show extra node info in report (see NODE INFO section)
89 Please refer to perf-report man page for details.
155 The perf c2c report command displays shared data analysis. It comes in two
158 The report command workflow is following:
164 In general perf report output consist of 2 basic views:
|
| D | perf-archive.txt | 22 linkperf:perf-record[1], linkperf:perf-buildid-list[1], linkperf:perf-report[1]
|
| D | callchain-overhead-calculation.txt | 45 in the usual (self-overhead-only) output of perf report:
66 calculate the 'children' overhead. In this case the report could be
107 'report.children = false' or 'top.children = false' in the perf config
|
| D | perf-report.txt | 1 perf-report(1)
6 perf-report - Read perf.data (created by perf record) and display the profile
11 'perf report' [-i <file> | --input=file]
192 field(s) to the default field order. For example: perf report -F +period,sample.
330 --cpu:: Only report samples for the list of CPUs provided. Multiple CPUs can
332 CPUs are specified with -: 0-2. Default is to report samples on all
359 perf report is able to auto-detect whether a perf.data file contains
439 perf report --time 10%/2
443 perf report --time 0%-10%
447 perf report --time 10%/1,10%/2
[all …]
|
| D | perf-evlist.txt | 45 linkperf:perf-report[1]
|
| D | perf-annotate.txt | 92 --cpu=<cpu>:: Only report samples for the list of CPUs provided. Multiple CPUs can
94 CPUs are specified with -: 0-2. Default is to report samples on all
138 linkperf:perf-record[1], linkperf:perf-report[1]
|
| D | intel-bts.txt | 72 perf report
75 By default, perf report will decode trace data found in the perf.data file.
|
| /tools/perf/tests/shell/ |
| D | record+zstd_comp_decomp.sh | 22 $perf_tool report -i $trace_file --header --stats | \
28 $perf_tool report -i $trace_file --stdio | head -n -3 > $trace_file.comp.output &&
29 $perf_tool report -i $trace_file.decomp --stdio | head -n -3 > $trace_file.decomp.output &&
|
| D | test_arm_coresight.sh | 57 perf report --stdio -i ${perfdata} | \
68 perf report --itrace=i1000i --stdio -i ${perfdata} | \
|
| /tools/testing/selftests/splice/ |
| D | short_splice_read.sh | 76 report="$4"
80 echo " matched $report" >&2
83 echo " no match: '$out' vs $report" >&2
|
| /tools/lib/subcmd/ |
| D | subcmd-util.h | 11 static inline void report(const char *prefix, const char *err, va_list params) in report() function
23 report(" Fatal: ", err, params); in die()
|
| /tools/testing/selftests/powerpc/pmu/ |
| D | count_instructions.c | 30 u64 overhead, bool report) in do_count_loop() argument
49 if (report) { in do_count_loop()
|
| D | count_stcx_fail.c | 30 u64 overhead, bool report) in do_count_loop() argument
51 if (report) { in do_count_loop()
|
| /tools/testing/selftests/kvm/x86_64/ |
| D | vmx_tsc_adjust_test.c | 122 static void report(int64_t val) in report() function
156 report(uc.args[1]); in main()
|
| /tools/testing/selftests/powerpc/pmu/ebb/ |
| D | instruction_count_test.c | 26 uint64_t overhead, bool report) in do_count_loop() argument
50 if (report) { in do_count_loop()
|