From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Loehle <christian.loehle@arm.com>
Cc: stable@vger.kernel.org, tj@kernel.org, arighi@nvidia.com,
void@manifault.com, sched-ext@lists.linux.dev
Subject: Re: [PATCH 1/2] sched_ext: Don't kick CPUs running higher classes
Date: Wed, 28 Jan 2026 15:18:58 +0100 [thread overview]
Message-ID: <2026012842-bubbling-busily-65bd@gregkh> (raw)
In-Reply-To: <20260124092043.349976-2-christian.loehle@arm.com>
On Sat, Jan 24, 2026 at 09:20:42AM +0000, Christian Loehle wrote:
> From: Tejun Heo <tj@kernel.org>
>
> commit a9c1fbbd6dadbaa38c157a07d5d11005460b86b9 upstream.
>
> When a sched_ext scheduler tries to kick a CPU, the CPU may be running a
> higher class task. sched_ext has no control over such CPUs. A sched_ext
> scheduler couldn't have expected to get access to the CPU after kicking it
> anyway. Skip kicking when the target CPU is running a higher class.
>
> Reviewed-by: Andrea Righi <arighi@nvidia.com>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> kernel/sched/ext.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
You did not sign off on these patches that you are forwarding on for us
to apply :(
next prev parent reply other threads:[~2026-01-28 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 9:20 [PATCH 0/2] SCX kick fixes from 6.19 Christian Loehle
2026-01-24 9:20 ` [PATCH 1/2] sched_ext: Don't kick CPUs running higher classes Christian Loehle
2026-01-28 14:18 ` Greg KH [this message]
2026-01-24 9:20 ` [PATCH 2/2] sched_ext: Fix SCX_KICK_WAIT to work reliably Christian Loehle
-- strict thread matches above, loose matches on Subject: below --
2026-01-29 9:25 [PATCHv2 0/2] SCX kick fixes from 6.19 Christian Loehle
2026-01-29 9:25 ` [PATCH 1/2] sched_ext: Don't kick CPUs running higher classes Christian Loehle
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=2026012842-bubbling-busily-65bd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arighi@nvidia.com \
--cc=christian.loehle@arm.com \
--cc=sched-ext@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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.