From: Andrea Righi <arighi@nvidia.com>
To: Zqiang <qiang.zhang@linux.dev>
Cc: tj@kernel.org, void@manifault.com, changwoo@igalia.com,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Use the resched_cpu() to replace resched_curr() in the bypass_lb_node()
Date: Mon, 22 Dec 2025 19:16:26 +0100 [thread overview]
Message-ID: <aUmK-moSOtQdD2VJ@gpd4> (raw)
In-Reply-To: <20251222115318.18997-1-qiang.zhang@linux.dev>
On Mon, Dec 22, 2025 at 07:53:17PM +0800, Zqiang wrote:
> For the PREEMPT_RT kernels, the scx_bypass_lb_timerfn() running in the
> preemptible per-CPU ktimer kthread context, this means that the following
> scenarios will occur(for x86 platform):
>
> cpu1 cpu2
> ktimer kthread:
> ->scx_bypass_lb_timerfn
> ->bypass_lb_node
> ->for_each_cpu(cpu, resched_mask)
>
> migration/1: by preempt by migration/2:
> multi_cpu_stop() multi_cpu_stop()
> ->take_cpu_down()
> ->__cpu_disable()
> ->set cpu1 offline
>
> ->rq1 = cpu_rq(cpu1)
> ->resched_curr(rq1)
> ->smp_send_reschedule(cpu1)
> ->native_smp_send_reschedule(cpu1)
> ->if(unlikely(cpu_is_offline(cpu))) {
> WARN(1, "sched: Unexpected
> reschedule of offline CPU#%d!\n", cpu);
> return;
> }
>
> This commit therefore use the resched_cpu() to replace resched_curr()
> in the bypass_lb_node() to avoid send-ipi to offline CPUs.
>
> Signed-off-by: Zqiang <qiang.zhang@linux.dev>
Good catch, resched_cpu() checks for online CPUs, so makes sense to me.
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Thanks,
-Andrea
> ---
> kernel/sched/ext.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
> index 5ebf8a740847..8f6d8d7f895c 100644
> --- a/kernel/sched/ext.c
> +++ b/kernel/sched/ext.c
> @@ -3956,13 +3956,8 @@ static void bypass_lb_node(struct scx_sched *sch, int node)
> nr_donor_target, nr_target);
> }
>
> - for_each_cpu(cpu, resched_mask) {
> - struct rq *rq = cpu_rq(cpu);
> -
> - raw_spin_rq_lock_irq(rq);
> - resched_curr(rq);
> - raw_spin_rq_unlock_irq(rq);
> - }
> + for_each_cpu(cpu, resched_mask)
> + resched_cpu(cpu);
>
> for_each_cpu_and(cpu, cpu_online_mask, node_mask) {
> u32 nr = READ_ONCE(cpu_rq(cpu)->scx.bypass_dsq.nr);
> --
> 2.17.1
>
next prev parent reply other threads:[~2025-12-22 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 11:53 [PATCH] sched_ext: Use the resched_cpu() to replace resched_curr() in the bypass_lb_node() Zqiang
2025-12-22 11:53 ` [PATCH] sched_ext: Avoid multiple irq_work_queue() calls in destroy_dsq() Zqiang
2025-12-22 18:30 ` Andrea Righi
2025-12-23 13:16 ` Zqiang
2025-12-23 4:00 ` Tejun Heo
2025-12-23 13:18 ` Zqiang
2025-12-22 18:16 ` Andrea Righi [this message]
2025-12-23 4:00 ` [PATCH] sched_ext: Use the resched_cpu() to replace resched_curr() in the bypass_lb_node() 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=aUmK-moSOtQdD2VJ@gpd4 \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.