From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Thomas Gleixner <tglx@kernel.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, aubrey.li@linux.intel.com,
yu.c.chen@intel.com
Subject: Re: [linus:master] [sched] 96d1610e0b: will-it-scale.per_process_ops 2.8% regression
Date: Fri, 24 Apr 2026 11:55:23 +0200 [thread overview]
Message-ID: <20260424095523.GE3126523@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <202604241448.365c92f9-lkp@intel.com>
On Fri, Apr 24, 2026 at 03:10:07PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed a 2.8% regression of will-it-scale.per_process_ops on:
>
>
> commit: 96d1610e0b20b5a627773874b4514ae922ad98f6 ("sched: Optimize hrtimer handling")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> [still regression on linus/master 1d51b370a0f8f642f4fc84c795fbedac0fcdbbd2]
> [still regression on linux-next/master 936c21068d7ade00325e40d82bfd2f3f29d9f659]
> [still regression on fix commit eef9f648fb0e92618041f019d4bdcf7ae17cb743]
>
> testcase: will-it-scale
> config: x86_64-rhel-9.4
> compiler: gcc-14
> test machine: 48 threads 2 sockets Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz (Ivy Bridge-EP) with 64G memory
> parameters:
So this commit has lived in private trees (tglx and mine), has been in
tip, in next etc. *WHY* do we only get this report now?
This isn't the first time I see a regression report after things have
hit Linus' tree. This is starting to get really annoying. The point of
having this robot was to catch issues *before* they hit Linus, no?
That said, looking back at will-it-scale reports, 2.8 seems to be pretty
much in the noise range, no?
next prev parent reply other threads:[~2026-04-24 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 7:10 [linus:master] [sched] 96d1610e0b: will-it-scale.per_process_ops 2.8% regression kernel test robot
2026-04-24 9:55 ` Peter Zijlstra [this message]
2026-04-27 5:59 ` Oliver Sang
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=20260424095523.GE3126523@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aubrey.li@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=tglx@kernel.org \
--cc=yu.c.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