[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160520153652.GA23195@krava>
Date: Fri, 20 May 2016 17:36:52 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: acme@...nel.org, jolsa@...nel.org, linux-kernel@...r.kernel.org,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] perf stat: Print topology/time headers with --metric-only
On Fri, May 20, 2016 at 07:29:59AM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@...ux.intel.com>
>
> When --metric-only is enabled there were no headers for the topology
> in interval mode. Fix this here.
>
> Before
>
> $ perf stat --metric-only -e cycles,instructions -a -I 1000
> 1.000554967 insn per cycle stalled cycles per insn
> 1.000554967 0.27
> 2.000862000 0.24
> 3.001354948 0.25
>
> After
>
> $ perf stat --metric-only -e cycles,instructions -a -I 1000
> 1.000554967 insn per cycle stalled cycles per insn
> 1.000554967 0.27
> 2.000862000 0.24
> 3.001354948 0.25
hum, I'm getting something else:
[jolsa@...-x3650m4-01 perf]$ sudo ./perf stat --topdown -I 1000 -a
nmi_watchdog enabled with topdown. May give wrong results.
Disable with echo 0 > /proc/sys/kernel/nmi_watchdog
# time core cpus
1.001710838 retiring bad speculation frontend bound backend bound
1.001710838 S0-C0 2 38.1% -0.0% 58.8% 3.1%
1.001710838 S0-C1 2 38.0% 0.0% 59.4% 2.5%
[jolsa@...-x3650m4-01 perf]$ sudo ./perf stat --metric-only -e cycles,instructions -a -I 1000
# time
1.000756338 insn per cycle stalled cycles per insn
1.000756338 0.32
2.001155562 0.30
jirka
Powered by blists - more mailing lists