All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Roman Sudarikov <roman.sudarikov@linux.intel.com>,
	0day robot <lkp@intel.com>, Kan Liang <kan.liang@linux.intel.com>,
	Alexander Antonov <alexander.antonov@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org
Subject: Re: [perf x86] b77491648e: will-it-scale.per_process_ops -2.1% regression
Date: Wed, 05 Feb 2020 12:47:06 -0800	[thread overview]
Message-ID: <87tv44danp.fsf@linux.intel.com> (raw)
In-Reply-To: <20200205123110.GN12867@shao2-debian> (kernel test robot's message of "Wed, 5 Feb 2020 20:31:10 +0800")

kernel test robot <rong.a.chen@intel.com> writes:

> Greeting,
>
> FYI, we noticed a -2.1% regression of will-it-scale.per_process_ops due to commit:
>
>
> commit: b77491648e6eb2f26b6edf5eaea859adc17f4dcc ("perf x86: Infrastructure for exposing an Uncore unit to PMON mapping")
> https://github.com/0day-ci/linux/commits/roman-sudarikov-linux-intel-com/perf-x86-Exposing-IO-stack-to-IO-PMON-mapping-through-sysfs/20200118-075508

Seems to be spurious bisect. I don't think that commit could change
anything performance related.

-Andi

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [perf x86] b77491648e: will-it-scale.per_process_ops -2.1% regression
Date: Wed, 05 Feb 2020 12:47:06 -0800	[thread overview]
Message-ID: <87tv44danp.fsf@linux.intel.com> (raw)
In-Reply-To: <20200205123110.GN12867@shao2-debian>

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

kernel test robot <rong.a.chen@intel.com> writes:

> Greeting,
>
> FYI, we noticed a -2.1% regression of will-it-scale.per_process_ops due to commit:
>
>
> commit: b77491648e6eb2f26b6edf5eaea859adc17f4dcc ("perf x86: Infrastructure for exposing an Uncore unit to PMON mapping")
> https://github.com/0day-ci/linux/commits/roman-sudarikov-linux-intel-com/perf-x86-Exposing-IO-stack-to-IO-PMON-mapping-through-sysfs/20200118-075508

Seems to be spurious bisect. I don't think that commit could change
anything performance related.

-Andi

  reply	other threads:[~2020-02-05 20:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 12:31 [perf x86] b77491648e: will-it-scale.per_process_ops -2.1% regression kernel test robot
2020-02-05 12:31 ` kernel test robot
2020-02-05 20:47 ` Andi Kleen [this message]
2020-02-05 20:47   ` Andi Kleen
2020-02-06  3:07   ` [LKP] " Li, Philip
2020-02-06  3:07     ` Li, Philip
2020-02-12 10:56   ` [LKP] " Chen, Rong A
2020-02-12 10:56     ` Chen, Rong A
2020-02-12 15:15     ` [LKP] " Liang, Kan
2020-02-12 15:15       ` Liang, Kan

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=87tv44danp.fsf@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=alexander.antonov@intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=roman.sudarikov@linux.intel.com \
    --cc=rong.a.chen@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.