[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210317215142.GB1369306@tassilo.jf.intel.com>
Date: Wed, 17 Mar 2021 14:51:42 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Jin Yao <yao.jin@...ux.intel.com>, jolsa@...nel.org,
peterz@...radead.org, mingo@...hat.com,
alexander.shishkin@...ux.intel.com, Linux-kernel@...r.kernel.org,
kan.liang@...el.com, yao.jin@...el.com
Subject: Re: [PATCH v2] perf stat: Align CSV output for summary mode
> If you care about not breaking existing scripts, then the output they
> get with what they use as command line options must continue to produce
> the same output.
It's not clear there are any useful ones (except for tools that handle
both). It's really hard to parse the previous mess. It's simply not
valid CSV.
That's why I'm arguing that keeping compatibility is not useful here.
We would be stuck with the broken mess as default forever.
-Andi
Powered by blists - more mailing lists