From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Wanwu Li <liwanwu9113@163.com>, <mingo@redhat.com>,
<peterz@infradead.org>, <juri.lelli@redhat.com>,
<vincent.guittot@linaro.org>, <tj@kernel.org>
Cc: <dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
<bsegall@google.com>, <mgorman@suse.de>, <vschneid@redhat.com>,
<linux-kernel@vger.kernel.org>, Wanwu Li <liwanwu@kylinos.cn>
Subject: Re: [PATCH] sched/core: Fix stale se.load when modifying nice value under sched_ext
Date: Tue, 14 Jul 2026 15:00:32 +0530 [thread overview]
Message-ID: <a9be847f-4949-4a15-bd88-9abb32be3c14@amd.com> (raw)
In-Reply-To: <20260714091327.3-1-liwanwu9113@163.com>
Hello Wanwu,
On 7/14/2026 2:43 PM, Wanwu Li wrote:
> [You don't often get email from liwanwu9113@163.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> From: Wanwu Li <liwanwu@kylinos.cn>
>
> When a task's nice value is modified while running under sched_ext
> scheduling class, set_load_weight() calls reweight_task() which only
> updates static_prio but leaves p->se.load unchanged because sched_ext
> does not use it. After switching back to CFS, the stale se.load leads
> to incorrect load weight calculation.
>
> Fix this by explicitly refreshing p->se.load for sched_ext tasks after
> calling reweight_task().
>
> Fixes: d32960528702 ("sched/fair: set_load_weight() must also call reweight_task() for SCHED_IDLE tasks")
> Signed-off-by: Wanwu Li <liwanwu@kylinos.cn>
Isn't this solved in
https://lore.kernel.org/lkml/20260528131238.3879110-1-quzicheng315@gmail.com/
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-07-14 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 9:13 Wanwu Li
2026-07-14 9:30 ` K Prateek Nayak [this message]
2026-07-14 9:48 ` liwanwu9113
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=a9be847f-4949-4a15-bd88-9abb32be3c14@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liwanwu9113@163.com \
--cc=liwanwu@kylinos.cn \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.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®