[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67ff59e77989445b876f90a2409bc7f8@honor.com>
Date: Tue, 19 Aug 2025 07:41:05 +0000
From: liuwenfang <liuwenfang@...or.com>
To: 'Tejun Heo' <tj@...nel.org>
CC: 'David Vernet' <void@...ifault.com>, 'Andrea Righi' <arighi@...dia.com>,
'Changwoo Min' <changwoo@...lia.com>, 'Ingo Molnar' <mingo@...hat.com>,
'Peter Zijlstra' <peterz@...radead.org>, 'Juri Lelli'
<juri.lelli@...hat.com>, 'Vincent Guittot' <vincent.guittot@...aro.org>,
'Dietmar Eggemann' <dietmar.eggemann@....com>, 'Steven Rostedt'
<rostedt@...dmis.org>, 'Ben Segall' <bsegall@...gle.com>, 'Mel Gorman'
<mgorman@...e.de>, 'Valentin Schneider' <vschneid@...hat.com>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 1/3] sched_ext: Fix pnt_seq calculation
Hello,
>
> Might as well match the surrounding naming convention and use
> __put_prev_set_next_scx()
It makes sense, and __put_prev_set_next_scx() has been changed to an inline function in [PATCH v4 1/3].
A changelog has been added accordingly.
switch_class() is renamed as scx_maybe_cpu_release() in [PATCH v4 3/3].
Also scx_maybe_cpu_acquire() is added in [PATCH v4 3/3].
However, scx_maybe_cpu_release() called in __put_prev_set_next_scx() is difficult to convert into an inline function in [PATCH v4 3/3].
look forward for your reply.
--
Regards.
Wenfang
Powered by blists - more mailing lists