linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: 'perf stat --repeat N' oddity/regression
Date: Mon, 25 Jan 2016 19:35:11 +0100	[thread overview]
Message-ID: <20160125183511.GA24981@gmail.com> (raw)
In-Reply-To: <20160125182206.GA11648@gmail.com>


So it appears it broke somewhere between v4.0 and v4.1, as the v4.0 install 
displays:

    16,244,802,268      instructions               ( +- 23.01% )

       2.108676769 seconds time elapsed                                          ( +-  0.86% )


[a few minutes later]

Bisected it down to:

 106a94a0f8c207ef4113ce7e32f34a00b3b174e7 is the first bad commit
 commit 106a94a0f8c207ef4113ce7e32f34a00b3b174e7
 Author: Jiri Olsa <jolsa@kernel.org>
 Date:   Fri Jun 26 11:29:19 2015 +0200

     perf stat: Introduce read_counters function

So this look like to be a regression.

Thanks,

	Ingo

  reply	other threads:[~2016-01-25 18:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 16:31 [PATCH] perf tools: Do not show trace command if it's not compiled in Jiri Olsa
2016-01-12 11:23 ` Ingo Molnar
2016-01-12 14:29   ` Arnaldo Carvalho de Melo
2016-01-13 10:42     ` Ingo Molnar
2016-01-25 18:22       ` 'perf stat --repeat N' oddity/regression Ingo Molnar
2016-01-25 18:35         ` Ingo Molnar [this message]
2016-01-25 19:43           ` Arnaldo Carvalho de Melo
2016-01-25 19:48             ` Arnaldo Carvalho de Melo
2016-01-26  8:08               ` Ingo Molnar
2016-01-26 14:18                 ` Arnaldo Carvalho de Melo

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=20160125183511.GA24981@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).