mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf stat stddev reporting broken since "perf stat: Introduce read_counters function"
Date: Tue, 19 Jan 2016 09:38:12 +0000	[thread overview]
Message-ID: <20160119093812.GD10802@techsingularity.net> (raw)
In-Reply-To: <20160119081623.GC20358@krava.brq.redhat.com>

On Tue, Jan 19, 2016 at 09:16:23AM +0100, Jiri Olsa wrote:
> On Tue, Jan 19, 2016 at 08:42:28AM +0100, Jiri Olsa wrote:
> 
> SNIP
> 
> > > 
> > >  Performance counter stats for 'sleep 1' (5 runs):
> > > 
> > >           0.583178      task-clock (msec)         #    0.001 CPUs utilized
> > >                  1      context-switches          #    0.002 M/sec
> > >                  0      cpu-migrations            #    0.000 K/sec
> > >                 67      page-faults               #    0.141 M/sec
> > >          1,224,416      cycles                    #    2.585 GHz
> > >    <not supported>      stalled-cycles-frontend
> > >    <not supported>      stalled-cycles-backend
> > >            892,568      instructions              #    0.68  insns per cycle
> > >            184,975      branches                  #  390.554 M/sec
> > >              8,512      branch-misses             #    4.57% of all branches
> > > 
> > >        1.000889249 seconds time elapsed                                          ( +-  0.01% )
> > > 
> > > I checked and current master in Linus' tree is also broken. Is this
> > > change in documented perf stat behaviour intentional?
> > 
> > nope, not intentional.. I'll check on that, thanks for reporting
> 
> for some reason we initialized the stat every iteration,
> (the call is also wrong because it's called only over the
> first res_stats[0])
> 
> attached patch works for me, could you please test?
> I'll run more tests and put it in my queue
> 

That works for me too, thanks. Feel free to put this on the patch;

Tested-by: Mel Gorman <mgorman@techsingularity.net>

When you send it through, can you make sure it has the following please?

Cc: stable@vger.kernel.org # v4.2+

-- 
Mel Gorman
SUSE Labs

  reply	other threads:[~2016-01-19  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 17:59 Mel Gorman
2016-01-19  7:42 ` Jiri Olsa
2016-01-19  8:16   ` Jiri Olsa
2016-01-19  9:38     ` Mel Gorman [this message]
2016-01-19  9:57       ` Jiri Olsa

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=20160119093812.GD10802@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=acme@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --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

Powered by JetHome