From: Thomas Gleixner <tglx@linutronix.de>
To: Philip Li <philip.li@intel.com>
Cc: Feng Tang <feng.tang@intel.com>,
"Song Bao Hua \(Barry Song\)" <song.bao.hua@hisilicon.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"lkp\@lists.01.org" <lkp@lists.01.org>,
"lkp\@intel.com" <lkp@intel.com>,
"zhengjun.xing\@intel.com" <zhengjun.xing@intel.com>,
"x86\@kernel.org" <x86@kernel.org>
Subject: Re: [LKP] Re: [genirq] cbe16f35be: will-it-scale.per_thread_ops -5.2% regression
Date: Wed, 28 Apr 2021 18:56:29 +0200 [thread overview]
Message-ID: <874kfqmjpe.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210428152339.GA2282261@pl-dbox>
Philip,
On Wed, Apr 28 2021 at 23:23, Philip Li wrote:
> On Wed, Apr 28, 2021 at 10:56:16AM +0200, Thomas Gleixner wrote:
>> On Wed, Apr 28 2021 at 16:08, Feng Tang wrote:
>> > On Wed, Apr 28, 2021 at 07:01:35AM +0000, Song Bao Hua (Barry Song) wrote:
>> >
>> >> But it is still an irrelevant problem.
>> > Yes, the commit itself has no problem. And my personal thought
>> > is no further action is needed.
>>
>> The commit does not need any further action, but this testing stuff
> Sorry Thomas for confusion and trouble caused by this. We will take it
> seriously to refine the report process for this category (alignment or
> cache behavior) of performance change, to avoid meaningless ones.
Things go wrong every now and then. As long as we figure it out and
stuff gets fixed, no problem.
Thanks,
tglx
prev parent reply other threads:[~2021-04-28 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 9:00 [genirq] cbe16f35be: will-it-scale.per_thread_ops -5.2% regression kernel test robot
2021-04-27 9:20 ` Song Bao Hua (Barry Song)
2021-04-27 11:37 ` Thomas Gleixner
2021-04-27 11:42 ` Thomas Gleixner
2021-04-27 19:37 ` Thomas Gleixner
2021-04-28 8:36 ` Feng Tang
2021-04-28 5:07 ` Feng Tang
2021-04-28 7:01 ` Song Bao Hua (Barry Song)
2021-04-28 8:08 ` Feng Tang
2021-04-28 8:56 ` Thomas Gleixner
2021-04-28 15:23 ` [LKP] " Philip Li
2021-04-28 16:56 ` Thomas Gleixner [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=874kfqmjpe.ffs@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mingo@kernel.org \
--cc=philip.li@intel.com \
--cc=song.bao.hua@hisilicon.com \
--cc=x86@kernel.org \
--cc=zhengjun.xing@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).