From: "Li, Philip" <philip.li@intel.com>
To: Andi Kleen <ak@linux.intel.com>, "Chen, Rong A" <rong.a.chen@intel.com>
Cc: Roman Sudarikov <roman.sudarikov@linux.intel.com>,
lkp <lkp@intel.com>, Kan Liang <kan.liang@linux.intel.com>,
"Antonov, Alexander" <alexander.antonov@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"lkp@lists.01.org" <lkp@lists.01.org>
Subject: RE: [LKP] Re: [perf x86] b77491648e: will-it-scale.per_process_ops -2.1% regression
Date: Thu, 6 Feb 2020 03:07:15 +0000 [thread overview]
Message-ID: <831EE4E5E37DCC428EB295A351E6624952397CEA@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <87tv44danp.fsf@linux.intel.com>
> Subject: [LKP] Re: [perf x86] b77491648e: will-it-scale.per_process_ops -2.1%
> regression
>
> 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.
Hi Andi, we will look into this as early as possible, we also receive another input from
Pater Z that he got false positive of will-it-scale.per_process_ops performance
regression. We will investigate them.
>
> -Andi
> _______________________________________________
> LKP mailing list -- lkp@lists.01.org
> To unsubscribe send an email to lkp-leave@lists.01.org
next prev parent reply other threads:[~2020-02-06 3:07 UTC|newest]
Thread overview: 5+ 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 20:47 ` Andi Kleen
2020-02-06 3:07 ` Li, Philip [this message]
2020-02-12 10:56 ` [LKP] " Chen, Rong A
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=831EE4E5E37DCC428EB295A351E6624952397CEA@shsmsx102.ccr.corp.intel.com \
--to=philip.li@intel.com \
--cc=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 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).