[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241030211104.GT9767@noisy.programming.kicks-ass.net>
Date: Wed, 30 Oct 2024 22:11:04 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Tejun Heo <tj@...nel.org>
Cc: mingo@...nel.org, juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, vschneid@...hat.com, void@...ifault.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 2/6] sched: Employ sched_change guards
On Wed, Oct 30, 2024 at 11:09:56AM -1000, Tejun Heo wrote:
> On Wed, Oct 30, 2024 at 10:58:40AM -1000, Tejun Heo wrote:
> > On Wed, Oct 30, 2024 at 04:12:57PM +0100, Peter Zijlstra wrote:
> > --- a/kernel/sched/ext.c
> > +++ b/kernel/sched/ext.c
> > @@ -4496,6 +4496,8 @@ static void scx_ops_disable_workfn(struc
> > const struct sched_class *new_class =
> > __setscheduler_class(p->policy, p->prio);
> >
> > + update_rq_clock(task_rq(p));
> > +
>
> Oh, this probably should be paired with DEQUEUE_NOCLOCK.
Yeah, it is like that at the end of the series. I'll shuffle things
around and make it so earlier.
Thanks!
Powered by blists - more mailing lists