[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <caa2329c-d985-4a7c-b83a-c4f96d5f154a@amd.com>
Date: Tue, 13 Jan 2026 09:42:25 +0530
From: K Prateek Nayak <kprateek.nayak@....com>
To: Pierre Gondois <pierre.gondois@....com>, Peter Zijlstra
<peterz@...radead.org>, <tj@...nel.org>
CC: <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
Hello Pierre,
On 1/13/2026 2:14 AM, Pierre Gondois wrote:
> Hello Peter,
>
> It seems this patch:
> 6455ad5346c9 ("sched: Move sched_class::prio_changed() into the change pattern")
> is triggering the following warning:
> rq_pin_lock()
> \-WARN_ON_ONCE(rq->balance_callback && rq->balance_callback != &balance_push_callback);
Can you check if the following solution helps your case too:
https://lore.kernel.org/all/20260106104113.GX3707891@noisy.programming.kicks-ass.net/
--
Thanks and Regards,
Prateek
Powered by blists - more mailing lists