From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754450AbdFNHUa (ORCPT ); Wed, 14 Jun 2017 03:20:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49930 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754122AbdFNHU2 (ORCPT ); Wed, 14 Jun 2017 03:20:28 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 283DD83F40 Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jolsa@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 283DD83F40 Date: Wed, 14 Jun 2017 09:20:24 +0200 From: Jiri Olsa To: David Carrillo-Cisneros Cc: linux-kernel , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Andi Kleen , Simon Que , Wang Nan , Jiri Olsa , He Kuang , Masami Hiramatsu , Stephane Eranian , Paul Turner Subject: Re: [PATCH v4 00/16] perf tool: add meta-data header support for pipe-mode Message-ID: <20170614072024.GB25037@krava> References: <20170613042932.141842-1-davidcc@google.com> <20170613185506.GF6092@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Wed, 14 Jun 2017 07:20:28 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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