[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260113115309.GB831050@noisy.programming.kicks-ass.net>
Date: Tue, 13 Jan 2026 12:53:09 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: K Prateek Nayak <kprateek.nayak@....com>
Cc: Pierre Gondois <pierre.gondois@....com>, tj@...nel.org,
linux-kernel@...r.kernel.org, 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, longman@...hat.com,
hannes@...xchg.org, mkoutny@...e.com, void@...ifault.com,
arighi@...dia.com, changwoo@...lia.com, cgroups@...r.kernel.org,
sched-ext@...ts.linux.dev, liuwenfang@...or.com, tglx@...utronix.de,
Christian Loehle <christian.loehle@....com>
Subject: Re: [PATCH 05/12] sched: Move sched_class::prio_changed() into the
change pattern
On Tue, Jan 13, 2026 at 04:35:02PM +0530, K Prateek Nayak wrote:
> Does enabling WARN_DOUBLE_CLOCK warn of a double clock update before
> hitting this warning?
setup_new_dl_entity() -> update_rq_clock() seems like it will trip that
in this case.
Powered by blists - more mailing lists