On Tue, Jun 13, 2017 at 11:51:43PM -0700, David Carrillo-Cisneros wrote: > On Tue, Jun 13, 2017 at 11:55 AM, Jiri Olsa <[email protected]> wrote: > > On Mon, Jun 12, 2017 at 09:29:16PM -0700, David Carrillo-Cisneros wrote: > >> v4: - Limit write_* functions to page_size. > >> - Fixed bugs spotted by Jiri. > >> - Add information about pipe-mode to some error messages. > > > > looks like this version breaks the normal report > > > > [jolsa@krava perf]$ ./perf report --header-only -I > > [jolsa@krava perf]$ > > Is the command simply terminating without any output? I cannot > reproduce it. In my machines it works: > > $ ./perf report --header-only -I > # ======== > # captured on: Tue Jun 13 23:49:13 2017 > # hostname : lphh20 > # os release : 4.3.5-smp-801.43.0.0 > # perf version : 4.12.rc4.gf2978e > # arch : x86_64 > # nrcpus online : 72 > # nrcpus avail : 72 > # cpudesc : Intel(R) Xeon(R) CPU E5-2696 v3 @ 2.30GHz > # cpuid : GenuineIntel,6,63,2 > # total memory : 264134144 kB > # cmdline : /root/perf record ls > # event : name = cycles:pp, , size = 112, { sample_period, sample_freq > } = 4000, sample_type = IP|TID|TIME|PERIOD, disa > # sibling cores : 0-17,36-53 > # sibling cores : 18-35,54-71 > [SNIP] > > Is your perf.data from the same version?
yes: [jolsa@krava perf]$ ./perf record kill kill: not enough arguments [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.016 MB perf.data (7 samples) ] [jolsa@krava perf]$ ./perf report --header-only -I [jolsa@krava perf]$ but I'm actualy using branch I found in your tree: ccdavid/toup_june12_pipeheaders_00, maybe it's not the latest [jolsa@krava perf]$ git log --oneline | head -1 a16f0acca1d2 perf header: add event desc to pipe-mode header jirka
