summaryrefslogtreecommitdiff
path: root/tools/lib/python/feat
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2026-05-10 23:08:16 +0300
committerTejun Heo <tj@kernel.org>2026-05-10 23:08:16 +0300
commit938dd9ab2bd7df0a7e58ce4249794156be9530b4 (patch)
tree211a1b01cd32851cd9f8e7ae392b6db6e13d275f /tools/lib/python/feat
parent6947bea4b79115f50138882512f85fa9c93b2827 (diff)
downloadlinux-938dd9ab2bd7df0a7e58ce4249794156be9530b4.tar.xz
sched_ext: Inline scx_init_task() and move RESET_RUNNABLE_AT into scx_set_task_state()
Prepare for the SCX_TASK_INIT_BEGIN/DEAD work that follows by collapsing the scx_init_task() helper. Move the SCX_TASK_RESET_RUNNABLE_AT setting into scx_set_task_state() on the INIT transition (it was set unconditionally at every INIT site through the scx_init_task() helper), inline scx_init_task() into scx_fork() and scx_root_enable_workfn(), and drop the helper. As a side effect, scx_sub_disable() migration sequence now also sets RESET_RUNNABLE_AT (it previously wrote INIT directly without going through scx_init_task()). The flag triggers a runnable_at reset on the next set_task_runnable(), which is harmless on a task that has just been moved between scheds. On root-enable, p->scx.flags is written without the task's rq lock. The task isn't visible to scx yet, and a follow-up patch restores the lock-held write. v2: Note p->scx.flags rq-lock relaxation on root-enable path. (Andrea) Signed-off-by: Tejun Heo <tj@kernel.org> Reviewed-by: Andrea Righi <arighi@nvidia.com>
Diffstat (limited to 'tools/lib/python/feat')
0 files changed, 0 insertions, 0 deletions