From: Vincent Guittot <vincent.guittot@linaro.org>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org
Cc: Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH] sched/fair: Always clear se->exec_start when migrated
Date: Fri, 20 Nov 2026 10:58:19 +0100 [thread overview]
Message-ID: <20261120095819.1009260-1-vincent.guittot@linaro.org> (raw)
Make sure that se->exec_start is always cleared when task migrates even
when migrating on a throttled cfs.
And remove useless clear of group_entities which can't migrate
Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
---
kernel/sched/fair.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 942140247f76..4e2674bc5c32 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -6555,10 +6555,6 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
account_entity_enqueue(cfs_rq, se);
- /* Entity has migrated, no longer consider this task hot */
- if (flags & ENQUEUE_MIGRATED)
- se->exec_start = 0;
-
check_schedstat_required();
update_stats_enqueue_fair(cfs_rq, se, flags);
se->on_rq = 1;
@@ -8214,6 +8210,10 @@ enqueue_task_fair(struct rq *rq, struct task_struct *p, int flags)
unsigned long weight;
bool curr;
+ /* Always clear exec_start when task migrated even for throttled one */
+ if (flags & ENQUEUE_MIGRATED)
+ se->exec_start = 0;
+
if (task_is_throttled(p) && enqueue_throttled_task(p))
return;
--
2.53.0
next reply other threads:[~2026-11-20 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 9:58 Vincent Guittot [this message]
2026-11-20 10:27 ` Kayra Cizmeci
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=20261120095819.1009260-1-vincent.guittot@linaro.org \
--to=vincent.guittot@linaro.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vschneid@redhat.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®