Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1236788
| From | Jiri Olsa <jolsa@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCHv2 00/45] perf stat: Add scripting support |
| Date | 2015-09-30 23:40 +0200 |
| Message-ID | <qexgu-oR-31@gated-at.bofh.it> (permalink) |
| References | <qeqoF-7qA-3@gated-at.bofh.it> <qewX8-8qQ-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Sep 30, 2015 at 09:09:39PM +0000, Liang, Kan wrote: SNIP > > Examples: > > > > - To record data for command stat workload: > > > > $ perf stat record kill > > ... > > > > Performance counter stats for 'kill': > > > > 0.372007 task-clock (msec) # 0.613 CPUs utilized > > 3 context-switches # 0.008 M/sec > > 0 cpu-migrations # 0.000 K/sec > > 62 page-faults # 0.167 M/sec > > 1,129,973 cycles # 3.038 GHz > > <not supported> stalled-cycles-frontend > > <not supported> stalled-cycles-backend > > 813,313 instructions # 0.72 insns per cycle > > 166,161 branches # 446.661 M/sec > > 8,747 branch-misses # 5.26% of all branches > > > > 0.000607287 seconds time elapsed > > > > The default file for perf stat record is perf.data. > It's easy to be mix up with the data file from perf record. > How about using perf.data.stat to instead? hum, I'm inclined to keep using the perf.data as default of whatever comes out of the perf.. and do the 'perf report' proxy based on the data you described in the next comment SNIP > > - To store system-wide period stat data: > > > > $ perf stat -e cycles:u,instructions:u -a -I 1000 record > > # time counts unit events > > 1.000265471 462,311,482 cycles:u (100.00%) > > 1.000265471 590,037,440 instructions:u > > 2.000483453 722,532,336 cycles:u (100.00%) > > 2.000483453 848,678,197 instructions:u > > 3.000759876 75,990,880 cycles:u (100.00%) > > 3.000759876 86,187,813 instructions:u > > ^C 3.213960893 85,329,533 cycles:u (100.00%) > > 3.213960893 135,954,296 instructions:u > > > > - To report perf stat data: > > > > Could we support perf report as well? > If I run perf report with the data file, there are some warnings. > We know the data file is from perf stat or perf record, so it should > be not hard to handle the warnings. well perf report wants to display sampling data which are not present.. probabbly complaining about sample_type I guess I think 'perf report' could check on perf.data and if it detects stat data proxy the handling to the perf stat report but not sure how to handle both commands options differencies ATM > Also it's better that all the new record type (CPU/THREAD_MAP, > STAT_CONFIG, STAT and etc) can be dumped by perf report -D. > It shows unhandled now. right, I'll those thanks, jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCHv2 00/45] perf stat: Add scripting support Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:20 +0200
[PATCH 44/45] perf script: Add python support for stat events Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:20 +0200
[PATCH 40/45] perf script: Process stat config event Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:20 +0200
[PATCH 05/45] perf tools: Add cpu_map event synthesize function Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:20 +0200
[PATCH 29/45] perf tools: Add data arg to cpu_map__build_map callback Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:20 +0200
[PATCH 34/45] perf stat report: Add support to initialize aggr_map from file Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:20 +0200
[PATCH 30/45] perf stat report: Cache aggregated map entries in extra cpumap Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:20 +0200
[PATCH 09/45] perf tools: Add stat config event read function Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 18/45] perf stat: Add AGGR_UNSET mode Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 11/45] perf tools: Add stat event synthesize function Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 17/45] perf stat: Rename perf_stat struct into perf_stat_evsel Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 23/45] perf stat record: Add pipe support for record command Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 12/45] perf tools: Add stat event read function Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 02/45] perf tools: Add thread_map event synthesize function Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 14/45] perf tools: Add stat round event synthesize function Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 15/45] perf tools: Introduce stat feature Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 04/45] perf tools: Add cpu_map event Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 22/45] perf stat record: Store events IDs in perf data file Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 08/45] perf tools: Add stat config event synthesize function Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 19/45] perf stat record: Add record command Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
[PATCH 21/45] perf stat record: Synthesize stat record data Jiri Olsa <jolsa@kernel.org> - 2015-09-30 16:30 +0200
RE: [PATCHv2 00/45] perf stat: Add scripting support "Liang, Kan" <kan.liang@intel.com> - 2015-09-30 23:20 +0200
Re: [PATCHv2 00/45] perf stat: Add scripting support Jiri Olsa <jolsa@redhat.com> - 2015-09-30 23:40 +0200
Re: [PATCHv2 00/45] perf stat: Add scripting support Jiri Olsa <jolsa@redhat.com> - 2015-09-30 23:40 +0200
csiph-web