From: "Henry Huang" <henry.hj@antgroup.com>
To: arighi@nvidia.com
Cc: changwoo@igalia.com, "Henry Huang" <henry.hj@antgroup.com>,
谈鉴锋 <henry.tjf@antgroup.com>,
linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
tj@kernel.org, void@manifault.com,
"Yan Yan(cailing)" <yanyan.yan@antgroup.com>
Subject: Re: [PATCH v1] sched_ext: include SCX_OPS_TRACK_MIGRATION
Date: Sun, 22 Jun 2025 22:55:26 +0800 [thread overview]
Message-ID: <20250622145526.21909-1-henry.hj@antgroup.com> (raw)
In-Reply-To: <aFf59XSp_kRexHvU@gpd4>
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
prev parent reply other threads:[~2025-06-22 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 9:36 [PATCH v1] " Henry Huang
2025-06-22 9:36 ` [PATCH v1] sched_ext: " Henry Huang
2025-06-22 12:41 ` Andrea Righi
2025-06-22 14:55 ` Henry Huang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250622145526.21909-1-henry.hj@antgroup.com \
--to=henry.hj@antgroup.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=henry.tjf@antgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--cc=yanyan.yan@antgroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®