linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Vince Weaver <vincent.weaver@maine.edu>,
	Jiri Olsa <jolsa@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Stephane Eranian <eranian@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org
Subject: Re: [perf/x86] 81ec3f3c4c: will-it-scale.per_process_ops -5.5% regression
Date: Wed, 5 Feb 2020 13:58:04 +0100	[thread overview]
Message-ID: <20200205125804.GM14879@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200205123216.GO12867@shao2-debian>

On Wed, Feb 05, 2020 at 08:32:16PM +0800, kernel test robot wrote:
> Greeting,
> 
> FYI, we noticed a -5.5% regression of will-it-scale.per_process_ops due to commit:
> 
> 
> commit: 81ec3f3c4c4d78f2d3b6689c9816bfbdf7417dbb ("perf/x86: Add check_period PMU callback")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 

I'm fairly sure this bisect/result is bogus.

  reply	other threads:[~2020-02-05 12:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 12:32 [perf/x86] 81ec3f3c4c: will-it-scale.per_process_ops -5.5% regression kernel test robot
2020-02-05 12:58 ` Peter Zijlstra [this message]
2020-02-06  3:04   ` [LKP] " Li, Philip
2020-02-21  8:03   ` Feng Tang
2020-02-21 10:58     ` Peter Zijlstra
2020-02-21 13:20     ` Jiri Olsa
2020-02-23 14:11       ` Feng Tang
2020-02-23 17:37         ` Linus Torvalds
2020-02-24  0:33           ` Feng Tang
2020-02-24  1:06             ` Linus Torvalds
2020-02-24  1:58               ` Huang, Ying
2020-02-24  2:19               ` Feng Tang
2020-02-24 13:20                 ` Feng Tang
2020-02-24 19:24                 ` Linus Torvalds
2020-02-24 19:42                   ` Kleen, Andi
2020-02-24 20:09                   ` Linus Torvalds
2020-02-24 20:47                     ` Linus Torvalds
2020-02-24 21:20                       ` Eric W. Biederman
2020-02-24 21:43                         ` Linus Torvalds
2020-02-24 21:59                           ` Eric W. Biederman
2020-02-24 22:12                             ` Linus Torvalds
2020-02-25  2:57                       ` Feng Tang
2020-02-25  3:15                         ` Linus Torvalds
2020-02-25  4:53                           ` Feng Tang
2020-02-23 19:36         ` Jiri Olsa
2020-02-21 18:05     ` Kleen, Andi
2020-02-22 12:43       ` Feng Tang
2020-02-22 17:08         ` Kleen, Andi

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=20200205125804.GM14879@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=mingo@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=rong.a.chen@intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.weaver@maine.edu \
    /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).