LKML Archive on lore.kernel.org
 help / color / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Kim Phillips <kim.phillips@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	lkp@lists.01.org
Subject: Re: [perf/x86/amd] 471af006a7: will-it-scale.per_process_ops -7.6% regression
Date: Fri, 14 Feb 2020 20:02:01 +0800
Message-ID: <ca326232-d084-3562-af78-1d9c6bdacd56@intel.com> (raw)
In-Reply-To: <20200212121830.GR14897@hirez.programming.kicks-ass.net>



On 2/12/2020 8:18 PM, Peter Zijlstra wrote:
> On Wed, Feb 12, 2020 at 07:35:14PM +0800, kernel test robot wrote:
>> Greeting,
>>
>> FYI, we noticed a -7.6% regression of will-it-scale.per_process_ops due to commit:
>>
>>
>> commit: 471af006a747f1c535c8a8c6c0973c320fe01b22 ("perf/x86/amd: Constrain Large Increment per Cycle events")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>
>> in testcase: will-it-scale
>> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 128G memory
> That commit only changes code relevant to AMD machines; give you have
> this result on an Intel machine makes me think the bisect is flawed.

Hi,

Sorry for the inconvenience, the regression is stable on our platform, 
we're investigating it.

Best Regards,
Rong Chen

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 11:35 kernel test robot
2020-02-12 12:18 ` Peter Zijlstra
2020-02-14 12:02   ` Chen, Rong A [this message]

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=ca326232-d084-3562-af78-1d9c6bdacd56@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=kim.phillips@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
	git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
	git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git