From: sashiko-bot@kernel.org
To: "Cui Jian" <cjian720@163.com>
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH] sched_ext:SCX is preemptible by the Fair scheduler
Date: Fri, 12 Jun 2026 16:28:18 +0000 [thread overview]
Message-ID: <20260612162818.C9C761F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260612161403.105775-1-cjian720@163.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch adds `SCX_CPU_PREEMPT_FAIR` to `enum scx_cpu_preempt_reason` in `kernel/sched/ext_internal.h`, but fails to update the checked-in autogenerated BPF tool headers in `tools/sched_ext/include/scx/enum_defs.autogen.h`.
--
commit 0e9cc05c20430d666c8c1a1d7ea0741d9c28b2d3
Author: Cui Jian <cjian720@163.com>
sched_ext:SCX is preemptible by the Fair scheduler
This commit adds a new preemption reason, SCX_CPU_PREEMPT_FAIR, to distinguish
when a sched_ext task is preempted by the Fair scheduler. It updates the
internal enum and mapping function to improve observability and diagnostics.
> diff --git a/kernel/sched/ext_internal.h b/kernel/sched/ext_internal.h
> index a075732d4430d..3ce07bec58a55 100644
> --- a/kernel/sched/ext_internal.h
> +++ b/kernel/sched/ext_internal.h
> @@ -241,6 +241,8 @@ enum scx_cpu_preempt_reason {
> SCX_CPU_PREEMPT_DL,
> /* next task is being scheduled by &sched_class_stop */
> SCX_CPU_PREEMPT_STOP,
> + /* next task is being scheduled by &sched_class_fair*/
> + SCX_CPU_PREEMPT_FAIR,
[Severity: Medium]
Should tools/sched_ext/include/scx/enum_defs.autogen.h be regenerated
and included in this patch?
When adding a new value to enum scx_cpu_preempt_reason, the autogenerated
BPF tool headers typically need updating so downstream BPF schedulers can
use feature detection macros like HAVE_SCX_CPU_PREEMPT_FAIR.
Without this update, BPF applications cannot conditionally check for this
new preemption feature across different kernel versions.
> /* unknown reason for SCX being preempted */
> SCX_CPU_PREEMPT_UNKNOWN,
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260612161403.105775-1-cjian720@163.com?part=1
next prev parent reply other threads:[~2026-06-12 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 16:14 [PATCH] sched_ext:SCX is preemptible by the Fair scheduler Cui Jian
2026-06-12 16:28 ` sashiko-bot [this message]
2026-06-12 16:32 ` Andrea Righi
[not found] ` <4a81ba55.9be4.19ebce4727a.Coremail.cjian720@163.com>
2026-06-12 18:18 ` Andrea Righi
-- strict thread matches above, loose matches on Subject: below --
2026-06-12 17:51 Cui Jian
2026-06-12 18:00 ` Andrea Righi
2026-06-12 18:05 ` sashiko-bot
2026-06-12 15:23 Cui Jian
2026-06-12 15:38 ` sashiko-bot
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=20260612162818.C9C761F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=cjian720@163.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sched-ext@lists.linux.dev \
/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