[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170321194948.GT32070@tassilo.jf.intel.com>
Date: Tue, 21 Mar 2017 12:49:48 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Andi Kleen <andi@...stfloor.org>, Jiri Olsa <jolsa@...hat.com>,
jolsa@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/13] perf, tools, stat: Output JSON MetricExpr metric
On Tue, Mar 21, 2017 at 04:42:45PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Mar 21, 2017 at 08:45:22AM -0700, Andi Kleen escreveu:
> > > > % perf stat -a -I 1000 -e '{unc_p_clockticks,unc_p_freq_max_os_cycles}' --metric-only
> > > > 1.000127077 0.9
> > > > 2.000301436 0.7
> > > > 3.000456379 0.0
> > >
> > > The comment above suggest I'll see 'original event as description' in this example??
> >
> > Yes the latest code prints
> >
> > % perf stat -a -I 1000 -e '{unc_p_clockticks,unc_p_freq_max_os_cycles}' --metric-only
> > # time freq_max_os_cycles %
> > 1.000234103 65.0
> > 2.000478612 75.2
> > 3.000681286 37.4
> > 4.000847224 2.9
>
> Ok, ammending that then, I guess that happened because you didn't left
> justified it with two spaces and git got it as a comment?
Yes that was it likely. I was wondering how it happened.
-Andi
Powered by blists - more mailing lists