[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 12 Dec 2019 10:41:40 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Jiri Olsa <jolsa@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Michael Petlan <mpetlan@...hat.com>,
Joe Mario <jmario@...hat.com>, Kajol Jain <kjain@...ux.ibm.com>
Subject: Re: [PATCH 3/3] perf stat: Add --metric option
On Wed, Dec 11, 2019 at 03:02:23PM -0800, Andi Kleen wrote:
> > Currently only one metric can be passed to perf stat command.
>
> It's near certain that users will want more.
right, it was just convenient for the rfc ;-)
but I wonder we could keep it that way anyway and have:
current way of using pre-defined metrics:
# perf stat -M m1,m2,m3
simple/fast way of checking on metric:
# perf stat -m 'm4=....'
metric from user file:
# perf stat -M m5,m6 --metric-file=path
thanks,
jirka
Powered by blists - more mailing lists