[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DEKD1W6CI6UJ.3TWR30PXQCF8O@google.com>
Date: Fri, 28 Nov 2025 13:26:30 +0000
From: Kuba Piecuch <jpiecuch@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>, <mingo@...nel.org>, <vincent.guittot@...aro.org>
Cc: <linux-kernel@...r.kernel.org>, <juri.lelli@...hat.com>,
<dietmar.eggemann@....com>, <rostedt@...dmis.org>, <bsegall@...gle.com>,
<mgorman@...e.de>, <vschneid@...hat.com>, <tj@...nel.org>,
<void@...ifault.com>, <arighi@...dia.com>, <changwoo@...lia.com>,
<sched-ext@...ts.linux.dev>
Subject: Re: [PATCH 5/5] sched: Rework sched_class::wakeup_preempt() and rq_modified_*()
Hi Peter,
On Thu Nov 27, 2025 at 3:39 PM UTC, Peter Zijlstra wrote:
> Additionally have set_next_task() re-set the value to the current class.
I don't see this part reflected in the patch. Is something missing?
Best,
Kuba
Powered by blists - more mailing lists