From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Waiman Long <longman@redhat.com>, Michal Hocko <mhocko@suse.com>,
Tejun Heo <tj@kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] sched: BUG() in select_fallback_rq() at boot with isolcpus=domain on the boot CPU and CONFIG_CPUSETS=n
Date: Wed, 18 Nov 2026 12:35:10 -0500 [thread overview]
Message-ID: <64f061ff-5a1d-44b3-a759-7daedfd67996@efficios.com> (raw)
In-Reply-To: <20261117150220.GG1813469@noisy.programming.kicks-ass.net>
Hi Peter,
On 2026-11-17 10:02, Peter Zijlstra wrote:
> Arguably, marking the boot cpu as isolated is asking for it. Is this
> really worth fixing? Or should we look for a better failure message?
A clear failure would be enough for me. Today the kernel hits a BUG()
in select_fallback_rq(), and nothing in the log points at isolcpus.
It is also a regression. The same command line boots with
CONFIG_CPUSETS=y. With CONFIG_CPUSETS=n, it boots with bf5b0c27fad2
("sched: Switch the fallback task allowed cpumask to HK_TYPE_DOMAIN")
reverted.
Waiman's plan to refuse domain isolation of the boot CPU would cover
both, if the refusal prints a message and the boot goes on. It changes
one setup that works today: isolcpus=domain,0,1 with CONFIG_CPUSETS=y.
Waiman, I can test a patch in the same VMs, with and without
CONFIG_CPUSETS.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2026-11-18 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 14:48 Mathieu Desnoyers
2026-11-17 15:02 ` Peter Zijlstra
2026-11-18 17:35 ` Mathieu Desnoyers [this message]
2026-11-17 15:13 ` Waiman Long
2026-11-18 14:49 ` Frederic Weisbecker
2026-11-18 15:55 ` Waiman Long
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=64f061ff-5a1d-44b3-a759-7daedfd67996@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®