mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>,
	Barry Song <song.bao.hua@hisilicon.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
	feng.tang@intel.com, zhengjun.xing@intel.com, x86@kernel.org
Subject: Re: [genirq]  cbe16f35be:  will-it-scale.per_thread_ops -5.2% regression
Date: Tue, 27 Apr 2021 13:42:12 +0200	[thread overview]
Message-ID: <87fszcnecr.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210427090013.GG32408@xsang-OptiPlex-9020>

Folks,

On Tue, Apr 27 2021 at 17:00, kernel test robot wrote:

> Greeting,
>
> FYI, we noticed a -5.2% regression of will-it-scale.per_thread_ops due to commit:
>
> commit: cbe16f35bee6880becca6f20d2ebf6b457148552 ("genirq: Add IRQF_NO_AUTOEN for request_irq/nmi()")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

this is the second report in the last week which makes not a lot of sense.
And this oneis makes absolutely no sense at all.

This commit affects request_irq() and the related variants and has
exactly ZERO influence on anything related to that test case simply
because.

I seriously have to ask the question whether this test infrastructure is
actually measuring what it claims to measure.

As this commit clearly _cannot_ have the 'measured' side effect, this
points to some serious issue in the tests or the test infrastructure
itself.

Thanks,

        tglx

  parent reply	other threads:[~2021-04-27 11:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  9:00 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 [this message]
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

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=87fszcnecr.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=oliver.sang@intel.com \
    --cc=song.bao.hua@hisilicon.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.com \
    --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
all inboxes | Powered by JetHome®