[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250622145526.21909-1-henry.hj@antgroup.com>
Date: Sun, 22 Jun 2025 22:55:26 +0800
From: "Henry Huang" <henry.hj@...group.com>
To: arighi@...dia.com
Cc: <changwoo@...lia.com>,
"Henry Huang" <henry.hj@...group.com>,
"谈鉴锋" <henry.tjf@...group.com>,
<linux-kernel@...r.kernel.org>,
<sched-ext@...ts.linux.dev>,
<tj@...nel.org>,
<void@...ifault.com>,
"Yan Yan(cailing)" <yanyan.yan@...group.com>
Subject: Re: [PATCH v1] sched_ext: include SCX_OPS_TRACK_MIGRATION
On Sun, 22 Jun 2025 14:41:25 +0200, Andrea Righi wrote:
> The overall change makes sense to me. I'm wondering if we should set
> DEQUEUE_MIGRATING here when task_on_rq_migrating(p) == true (apparently the
> sched core doesn't set this flag).
>
> In this way we can use ENQUEUE_MIGRATING and DEQUEUE_MIGRATING to
> distinguish between a migration ops.runnable/quiescent() call vs a
> "regular" one.
Thanks, I'll implement this in patch v2.
--
Henry
Powered by blists - more mailing lists