From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>
Cc: void@manifault.com, changwoo@igalia.com,
linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
peterz@infradead.org
Subject: Re: [PATCHSET RESEND v2 sched_ext/for-6.19] sched_ext: Fix SCX_KICK_WAIT reliability
Date: Wed, 22 Oct 2025 23:18:03 +0200 [thread overview]
Message-ID: <aPlKCzr8i0Ggow1O@gpd4> (raw)
In-Reply-To: <20251022205629.845930-1-tj@kernel.org>
Hi Tejun,
On Wed, Oct 22, 2025 at 10:56:26AM -1000, Tejun Heo wrote:
> Resending because the original v2 posting didn't include the full recipient
> list on the individual patches due to git send-email invocation error. Sorry
> about the noise.
>
> SCX_KICK_WAIT is used to synchronously wait for the target CPU to complete
> a reschedule and can be used to implement operations like core scheduling.
> However, recent scheduler refactorings broke its reliability. This series
> fixes the issue and improves the code clarity.
>
> v2: - In patch #2, also increment pnt_seq in pick_task_scx() to handle
> same-task re-selection (Andrea Righi).
> - In patch #2, use smp_cond_load_acquire() for the busy-wait loop for
> better architecture optimization (Peter Zijlstra).
> - Added patch #3 to rename pnt_seq to kick_sync for clarity.
>
> v1: http://lkml.kernel.org/r/20251021210354.89570-1-tj@kernel.org
Looks good to me!
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Thanks,
-Andrea
>
> Based on sched_ext/for-6.19 (2dbbdeda77a6).
>
> 1 sched_ext: Don't kick CPUs running higher classes
> 2 sched_ext: Fix SCX_KICK_WAIT to work reliably
> 3 sched_ext: Rename pnt_seq to kick_sync
>
> Git tree: git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-fix-kick_wait
>
> kernel/sched/ext.c | 129 ++++++++++++++++++++++++--------------------
> kernel/sched/ext_internal.h | 6 ++-
> kernel/sched/sched.h | 2 +-
> 3 files changed, 75 insertions(+), 62 deletions(-)
>
> --
> tejun
next prev parent reply other threads:[~2025-10-22 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 20:56 [PATCHSET RESEND v2 sched_ext/for-6.19] sched_ext: Fix SCX_KICK_WAIT reliability Tejun Heo
2025-10-22 20:56 ` [PATCH RESEND v2 1/3] sched_ext: Don't kick CPUs running higher classes Tejun Heo
2025-10-22 20:56 ` [PATCH RESEND v2 2/3] sched_ext: Fix SCX_KICK_WAIT to work reliably Tejun Heo
2025-10-22 20:56 ` [PATCH RESEND v2 3/3] sched_ext: Rename pnt_seq to kick_sync Tejun Heo
2025-10-22 21:18 ` Andrea Righi [this message]
2025-10-22 21:47 ` [PATCH v2] sched_ext: Fix SCX_KICK_WAIT reliability 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=aPlKCzr8i0Ggow1O@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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