public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf stat: Print topology/time headers with --metric-only
Date: Fri, 20 May 2016 17:47:38 +0200	[thread overview]
Message-ID: <20160520154738.GA26186@krava> (raw)
In-Reply-To: <20160520154319.GW11177@tassilo.jf.intel.com>

On Fri, May 20, 2016 at 08:43:19AM -0700, Andi Kleen wrote:
> > hum, I'm getting something else:
> > 
> > [jolsa@ibm-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@ibm-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                                      
> 
> Right sorry, that was me not cutting and pasting correctly.
> 
> Your output is correct and intended. 

hum, I dont think so.. headers should be on the same line, right?

jirka

  reply	other threads:[~2016-05-20 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 14:29 [PATCH] perf stat: Print topology/time headers with --metric-only Andi Kleen
2016-05-20 15:36 ` Jiri Olsa
2016-05-20 15:43   ` Andi Kleen
2016-05-20 15:47     ` Jiri Olsa [this message]
2016-05-20 19:53       ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160520154738.GA26186@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox