From: Sean Christopherson <seanjc@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
sched-ext@lists.linux.dev, aubrey.li@linux.intel.com,
yu.c.chen@intel.com
Subject: Re: [linus:master] [sched/core] 704069649b: kernel-selftests.kvm.hardware_disable_test.fail
Date: Fri, 13 Feb 2026 14:06:13 -0800 [thread overview]
Message-ID: <aY-gVWbdPUUQmcUR@google.com> (raw)
In-Reply-To: <20260213104006.GK3016024@noisy.programming.kicks-ass.net>
On Fri, Feb 13, 2026, Peter Zijlstra wrote:
> On Thu, Feb 12, 2026 at 10:08:04PM +0800, kernel test robot wrote:
> > we found the kernel-selftests.kvm.hardware_disable_test failed consistently upon
> > this commit but pass on parent. unfortunately, we didn't find many useful
> > information in dmesg. this report is just FYI what we observed in our tests.
> >
> > kernel test robot noticed "kernel-selftests.kvm.hardware_disable_test.fail" on:
> >
> > commit: 704069649b5bfb7bf1fe32c0281fe9036806a59a ("sched/core: Rework sched_class::wakeup_preempt() and rq_modified_*()")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> So this commit has been in tip (and thus -next) since 17 Dev '25. How
> come this is only reported now?
Well, on my end, I still don't do a good job of testing linux-next. But AFAICT,
it wouldn't have mattered in this case, because I probably wouldn't have noticed
given the nature of the failure and how I run KVM selftests.
next prev parent reply other threads:[~2026-02-13 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 14:08 [linus:master] [sched/core] 704069649b: kernel-selftests.kvm.hardware_disable_test.fail kernel test robot
2026-02-13 10:40 ` Peter Zijlstra
2026-02-13 22:06 ` Sean Christopherson [this message]
2026-02-13 14:44 ` Peter Zijlstra
2026-02-13 22:14 ` Sean Christopherson
2026-02-18 9:40 ` Peter Zijlstra
2026-02-18 16:33 ` Peter Zijlstra
2026-02-23 10:25 ` [tip: sched/urgent] sched/core: Fix wakeup_preempt's next_class tracking tip-bot2 for Peter Zijlstra
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=aY-gVWbdPUUQmcUR@google.com \
--to=seanjc@google.com \
--cc=aubrey.li@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.