[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210817195654.lrrytkgs42zcvr62@two.firstfloor.org>
Date: Tue, 17 Aug 2021 12:56:56 -0700
From: Andi Kleen <andi@...stfloor.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Andi Kleen <andi@...stfloor.org>,
Claire Jensen <cjense@...gle.com>, peterz@...radead.org,
mingo@...hat.com, acme@...nel.org, mark.rutland@....com,
alexander.shishkin@...ux.intel.com, jolsa@...hat.com,
namhyung@...nel.org, yao.jin@...ux.intel.com, song@...nel.org,
adrian.hunter@...el.com, kan.liang@...ux.intel.com,
james.clark@....com, alexander.antonov@...ux.intel.com,
changbin.du@...el.com, liuqi115@...wei.com, eranian@...gle.com,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
clairej735@...il.com
Subject: Re: [PATCH v2 1/1] perf stat: Add JSON output option.
> CSV:
> https://lore.kernel.org/lkml/20210813220936.2105426-1-cjense@google.com/
>
> json:
> https://lore.kernel.org/lkml/20210813220936.2105426-1-cjense@google.com/
How about --metric-only?
That's another completely different output mode.
Yes agreed a refactor would be useful, but it's a longer term project.
BTW we have similar problems with perf report and perf script output,
but stat is probably the worst.
-Andi
Powered by blists - more mailing lists