[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aWd4GNyU75K_CcTF@jlelli-thinkpadt14gen4.remote.csb>
Date: Wed, 14 Jan 2026 12:03:52 +0100
From: Juri Lelli <juri.lelli@...hat.com>
To: Yuri Andriaccio <yurand2000@...il.com>
Cc: Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Valentin Schneider <vschneid@...hat.com>,
linux-kernel@...r.kernel.org,
Luca Abeni <luca.abeni@...tannapisa.it>,
Yuri Andriaccio <yuri.andriaccio@...tannapisa.it>
Subject: Re: [RFC PATCH v4 01/28] sched/deadline: Do not access dl_se->rq
directly
Hello!
And Happy New Year! :)
On 01/12/25 13:41, Yuri Andriaccio wrote:
> From: luca abeni <luca.abeni@...tannapisa.it>
>
> Make deadline.c code access the runqueue of a scheduling entity saved in
> the sched_dl_entity data structure. This allows future patches to save
> different runqueues in sched_dl_entity other than the global runqueues.
>
> Move dl_server_apply_params call in sched_init_dl_servers as the
> rq_of_dl_se function will return the correct deadline entity only if the
> dl_server flag is set.
s/deadline entity/runqueue/ in the above, right?
> Add a WARN_ON on the return value of dl_server_apply_params in
> sched_init_dl_servers as this function may fail if the kernel is not
> configured correctly.
>
> Signed-off-by: luca abeni <luca.abeni@...tannapisa.it>
> Signed-off-by: Yuri Andriaccio <yurand2000@...il.com>
Apart from that
Reviewed-by: Juri Lelli <juri.lelli@...hat.com>
Thanks!
Juri
Powered by blists - more mailing lists