[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <48cca942-6b35-48b3-91bd-770265521203@web.de>
Date: Mon, 29 Sep 2025 13:03:32 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Alessio Balsini <a.balsini@...up.it>,
Andrea Parri <parri.andrea@...il.com>,
Luca Abeni <luca.abeni@...tannapisa.it>,
Yuri Andriaccio <yurand2000@...il.com>, kernel-janitors@...r.kernel.org
Cc: Yuri Andriaccio <yuri.andriaccio@...tannapisa.it>,
LKML <linux-kernel@...r.kernel.org>, Ben Segall <bsegall@...gle.com>,
Dietmar Eggemann <dietmar.eggemann@....com>, Ingo Molnar <mingo@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>, Mel Gorman <mgorman@...e.de>,
Peter Zijlstra <peterz@...radead.org>, Steven Rostedt <rostedt@...dmis.org>,
Valentin Schneider <vschneid@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>
Subject: Re: [RFC PATCH v3 13/24] sched/rt: Update rt-cgroup schedulability
checks
…
> +++ b/kernel/sched/deadline.c
> @@ -340,6 +340,39 @@ void cancel_inactive_timer(struct sched_dl_entity *dl_se)
…
> +#ifdef CONFIG_RT_GROUP_SCHED
> +void dl_init_tg(struct sched_dl_entity *dl_se, u64 rt_runtime, u64 rt_period)
> +{
…
> + u64 new_bw;
> +
> + raw_spin_rq_lock_irq(rq);
…
> + raw_spin_rq_unlock_irq(rq);
> +}
> +#endif
…
How do you think about to define and use a corresponding lock guard?
Regards,
Markus
Powered by blists - more mailing lists