From: "Emil Tsalapatis" <emil@etsalapatis.com>
To: "Emil Tsalapatis" <emil@etsalapatis.com>,
"Zqiang" <qiang.zhang@linux.dev>, <tj@kernel.org>,
<void@manifault.com>, <arighi@nvidia.com>, <changwoo@igalia.com>
Cc: <sched-ext@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched_ext: Remove unused code in the do_pick_task_scx()
Date: Mon, 15 Dec 2025 10:06:41 -0500 [thread overview]
Message-ID: <DEYVTV95347Z.14PG6TGXWB4XE@etsalapatis.com> (raw)
In-Reply-To: <DEYVT9MLT9MB.2GOBKYGZJ495Z@etsalapatis.com>
On Mon Dec 15, 2025 at 10:05 AM EST, Emil Tsalapatis wrote:
> On Mon Dec 15, 2025 at 6:29 AM EST, Zqiang wrote:
>> The kick_idle variable is no longer used, this commit therefore remove
>> it and also remove associated code in the do_pick_task_scx().
>>
>> Fixes: 4c95380701f5 ("sched/ext: Fold balance_scx() into pick_task_scx()"),
>> Signed-off-by: Zqiang <qiang.zhang@linux.dev>
>
> The change seems reasonable, but why is there a fixes up? This is
> followup cleanup, the original patch is perfectly fine.
>
Oh and of course tag aside:
Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
>> ---
>> kernel/sched/ext.c | 8 ++------
>> 1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
>> index 695503a2f7d1..94164f2dec6d 100644
>> --- a/kernel/sched/ext.c
>> +++ b/kernel/sched/ext.c
>> @@ -2446,7 +2446,7 @@ static struct task_struct *
>> do_pick_task_scx(struct rq *rq, struct rq_flags *rf, bool force_scx)
>> {
>> struct task_struct *prev = rq->curr;
>> - bool keep_prev, kick_idle = false;
>> + bool keep_prev;
>> struct task_struct *p;
>>
>> /* see kick_cpus_irq_workfn() */
>> @@ -2488,12 +2488,8 @@ do_pick_task_scx(struct rq *rq, struct rq_flags *rf, bool force_scx)
>> refill_task_slice_dfl(rcu_dereference_sched(scx_root), p);
>> } else {
>> p = first_local_task(rq);
>> - if (!p) {
>> - if (kick_idle)
>> - scx_kick_cpu(rcu_dereference_sched(scx_root),
>> - cpu_of(rq), SCX_KICK_IDLE);
>> + if (!p)
>> return NULL;
>> - }
>>
>> if (unlikely(!p->scx.slice)) {
>> struct scx_sched *sch = rcu_dereference_sched(scx_root);
next prev parent reply other threads:[~2025-12-15 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 11:29 Zqiang
2025-12-15 13:58 ` Andrea Righi
2025-12-15 15:05 ` Emil Tsalapatis
2025-12-15 15:06 ` Emil Tsalapatis [this message]
2025-12-15 15:57 ` Tejun Heo
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=DEYVTV95347Z.14PG6TGXWB4XE@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.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®