[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fszcnecr.ffs@nanos.tec.linutronix.de>
Date: Tue, 27 Apr 2021 13:42:12 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: kernel test robot <oliver.sang@...el.com>,
Barry Song <song.bao.hua@...ilicon.com>
Cc: Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org,
lkp@...el.com, ying.huang@...el.com, feng.tang@...el.com,
zhengjun.xing@...el.com, x86@...nel.org
Subject: Re: [genirq] cbe16f35be: will-it-scale.per_thread_ops -5.2% regression
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
Powered by blists - more mailing lists