Received: by 10.223.185.116 with SMTP id b49csp5277811wrg; Wed, 7 Mar 2018 09:06:19 -0800 (PST) X-Google-Smtp-Source: AG47ELvOl/J1kX6zUmcII/76cfjQTjIe2hBan8o/gcFsDOnSIVkUpUEwPbaI6RJVx1bq/ZpHgYpE X-Received: by 2002:a17:902:8302:: with SMTP id bd2-v6mr995122plb.322.1520442379429; Wed, 07 Mar 2018 09:06:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520442379; cv=none; d=google.com; s=arc-20160816; b=k+T8CqxGEVCTxWFnUQxpQv7HpH0qaBskls6Rle4Gz3UYn9trgNl0urDOD7wLydaktS QMgfkBv2rhqUSudkDQ1DenzRWA3g1Cz4JTN7JpzHroOhoOVCBtgYWEzMn8pyz9EfBD6Y 0XMp183TclBIAdx+vEs2+22Q+BfJ4zzjyHd7ZpZ4fuQXG6UlGc2GGLIYsyCmVu0HnJnX WdfIZVhvsIZTgcbi0ae2wLEYsHaN2wD3SXId1XqilEnDc6ctvRwvOEUFJzDr0j1SZXTW KCev9GjijEgQXdb/YMI0qRJXD7ZMS0O5jOtglqMK6RmfMHErdFe4S9XJeW6zZo4q/jMw bnhw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=O3hK6gm6jaKA/PQrOJobPxSOKe62084kFxHMKaU+b1c=; b=Qs1ZJIpRQdGSGaPoi/AAA8FSc4TI1xigZIuWNCsZImg4Tyddg/gaZNCw3eSyDEt+Yp /sD+GGLYf4IicWhbHYh8iY1safXNzbldwE0twF6RkPywjof5G3WoTk3cSzRBMMtkDC4n /ijKHN/wt86d8dhoRzWyAqzhAHpPAbwWEkEOPgluhMSBb/v/XMiIOZ03IYnn0An7Dpk5 Xq+n67AAwjDV1TbnK8tlxZxvouQgpOpLJWC26tXDxx9wCOtkht5VlA7OYExm6NibX7e9 tt4Xq8HQ2itFxsmkN5ztjN005Wb16hK5j+FEB0bHjsz2HsWDvqXk5AtrfGgLigGWB1LN +r/w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i136si11622589pgc.416.2018.03.07.09.06.03; Wed, 07 Mar 2018 09:06:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934017AbeCGREh (ORCPT + 99 others); Wed, 7 Mar 2018 12:04:37 -0500 Received: from mga11.intel.com ([192.55.52.93]:18004 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933487AbeCGRE1 (ORCPT ); Wed, 7 Mar 2018 12:04:27 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2018 09:04:26 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,436,1515484800"; d="scan'208";a="23286036" Received: from tassilo.jf.intel.com (HELO tassilo.localdomain) ([10.7.201.133]) by orsmga008.jf.intel.com with ESMTP; 07 Mar 2018 09:04:26 -0800 Received: by tassilo.localdomain (Postfix, from userid 1000) id 150A530053E; Wed, 7 Mar 2018 09:04:11 -0800 (PST) Date: Wed, 7 Mar 2018 09:04:11 -0800 From: Andi Kleen To: Ilya Pronin Cc: Cong Wang , LKML , Arnaldo Carvalho de Melo , Jiri Olsa Subject: Re: [PATCH] perf stat: fix cvs output format Message-ID: <20180307170411.GI25017@tassilo.jf.intel.com> References: <20180306064353.31930-1-xiyou.wangcong@gmail.com> <20180306170011.GD25017@tassilo.jf.intel.com> <20180306175320.GE25017@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 06, 2018 at 12:31:03PM -0800, Ilya Pronin wrote: > Speaking from the user's seat. An optional (not just empty) cgroup > field is fine as long it consistently appears when requested with -G > option. The problem with print_metric_csv() was that in the case of > unsupported counters 2 additional empty fields in the output are > completely unexpected and not documented anywhere. > > Andi, in the output example in your commit > 92a61f6412d3a09d6462252a522fa79c9290f405 stalled-cycles-backend event > has counter run time field, counter run time percentage field, empty > metric value, empty metric unit, and then 2 other empty fields. Are > they expected? If yes, what are they and why other events, e.g. No two extra empty fields are not expected. All lines should have the same number of fields so that a tool that looks at the first like can keep using the same number. But I don't think that was it what the patch fixed, or did I misread it? -Andi