From: Peter Zijlstra <peterz@infradead.org>
To: Kayra Cizmeci <kayracizmeci@gmail.com>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
kprateek.nayak@amd.com, joshdon@google.com, tj@kernel.org,
jakub@okonski.org
Subject: Re: [PATCH 2/3] sched/fair: Make cfs_rq::idle the sum of ancestor tg::idle
Date: Thu, 12 Nov 2026 16:10:10 +0100 [thread overview]
Message-ID: <20261112151010.GB1813469@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <avXFHBcVoMkZY6uL@scheduler.schedules>
On Thu, Nov 12, 2026 at 05:02:27PM +0300, Kayra Cizmeci wrote:
> :-(.
>
> Look here: https://lore.kernel.org/oe-kbuild-all/202611121431.06YgiErz-lkp@intel.com/
>
> On Thu, Nov 05, 2026 at 05:55:27PM +0100, Peter Zijlstra wrote:
> > Rather than keeping cfs_rq::idle as a copy of tg::idle, make it the sum of
> > all ancestor tg::idle. This makes it trivial to tell if the current cgroup
> > is marked idle somewhere along its ancestral path.
> >
> > This makes se_id_idle() behave differently. Notably is will now be true
> > when there is a idle cgroup anywhere in the ancestor path. This
> > addresses an issue where preemption of cgroup::idle was overlooked when
> > flattening the runqueue.
> >
> > Fixes: 85570f10a4c6 ("sched/eevdf: Move to a single runqueue")
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > ---
> > kernel/sched/core.c | 2 -
> > kernel/sched/debug.c | 1
> > kernel/sched/fair.c | 73 ++++++++++++++++++++++++++++++++-------------------
> > kernel/sched/sched.h | 4 +-
> > 4 files changed, 50 insertions(+), 30 deletions(-)
> >
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -8970,7 +8970,7 @@ void __init sched_init(void)
> > rq->nr_running = 0;
> > rq->calc_load_active = 0;
> > rq->calc_load_update = jiffies + LOAD_FREQ;
> > - init_cfs_rq(&rq->cfs);
> > + init_cfs_rq(&rq->cfs, NULL);
> > init_rt_rq(&rq->rt);
> > init_dl_rq(&rq->dl);
> > #ifdef CONFIG_FAIR_GROUP_SCHED
> > --- a/kernel/sched/debug.c
> > +++ b/kernel/sched/debug.c
> > @@ -1090,6 +1090,7 @@ void print_cfs_rq(struct seq_file *m, in
> > SEQ_printf(m, " .%-30s: %d\n", "h_nr_runnable", cfs_rq->h_nr_runnable);
> > SEQ_printf(m, " .%-30s: %d\n", "h_nr_queued", cfs_rq->h_nr_queued);
> > SEQ_printf(m, " .%-30s: %d\n", "h_nr_idle", cfs_rq->h_nr_idle);
> > + SEQ_printf(m, " .%-30s: %d\n", "idle", cfs_rq->idle);
>
> idle is only in the CONFIG_FAIR_GROUP_SCHED :-(.
> So as the robot says, this breaks compiling in !CONFIG_FAIR_GROUP_SCHED.
>
> AFAICT tho, moving this down below in CONFIG_FAIR_GROUP_SCHED next to
> h_load and other guys will solve the issue no?
Yeah, pushed out again, lets see if the robots find more ;-)
next prev parent reply other threads:[~2026-11-12 15:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 16:55 [PATCH 0/3] sched/fair: Fix cgroup::idle preemption Peter Zijlstra
2026-11-05 16:55 ` [PATCH 1/3] sched/fair: Use guard in sched_group_set_idle() Peter Zijlstra
2026-11-05 17:42 ` Kayra Cizmeci
2026-11-06 16:04 ` Vincent Guittot
2026-11-09 23:31 ` Josh Don
2026-11-05 16:55 ` [PATCH 2/3] sched/fair: Make cfs_rq::idle the sum of ancestor tg::idle Peter Zijlstra
2026-11-05 19:20 ` Kayra Cizmeci
2026-11-06 8:31 ` Peter Zijlstra
2026-11-06 8:53 ` Peter Zijlstra
2026-11-06 9:01 ` Kayra Cizmeci
2026-11-06 8:57 ` Kayra Cizmeci
2026-11-06 9:01 ` Peter Zijlstra
2026-11-06 9:11 ` Kayra Cizmeci
2026-11-06 16:24 ` Vincent Guittot
2026-11-07 11:36 ` [PATCH v2 " Peter Zijlstra
2026-11-07 13:13 ` Kayra Cizmeci
2026-11-09 10:13 ` Vincent Guittot
2026-11-09 23:50 ` Josh Don
2026-11-12 14:02 ` [PATCH " Kayra Cizmeci
2026-11-12 15:10 ` Peter Zijlstra [this message]
2026-11-05 16:55 ` [RFC][PATCH 3/3] sched/eevdf: Fix sched idle task group preemption Peter Zijlstra
2026-11-05 20:10 ` Kayra Cizmeci
2026-11-07 13:28 ` Kayra Cizmeci
2026-11-10 0:10 ` Josh Don
2026-11-10 14:20 ` Kayra Cizmeci
2026-11-10 17:51 ` Josh Don
2026-11-12 12:31 ` Peter Zijlstra
2026-11-12 12:38 ` 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=20261112151010.GB1813469@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jakub@okonski.org \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=kayracizmeci@gmail.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.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®