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 15:38:42 +0000 [thread overview]
Message-ID: <20260612153843.302E81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260612152304.94821-1-cjian720@163.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The autogenerated header enum_defs.autogen.h was not updated to include HAVE_SCX_CPU_PREEMPT_FAIR.
--
commit 6eebc3231d63fa92ff2758fc84fe12b421fbde6c
Author: Cui Jian <cjian720@163.com>
sched_ext:SCX is preemptible by the Fair scheduler
This commit adds a new SCX_CPU_PREEMPT_FAIR preempt reason for the sched_ext
subsystem. It updates the internal enum and preempt reason mapping to make it
easier to observe when a task is preempted by the Fair scheduler.
[ ... ]
> diff --git a/kernel/sched/ext_internal.h b/kernel/sched/ext_internal.h
> --- 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 also be updated in
this patch to include HAVE_SCX_CPU_PREEMPT_FAIR?
Without adding this to the autogenerated header, external BPF schedulers
cannot use #ifdef HAVE_SCX_CPU_PREEMPT_FAIR to safely compile and support
both old and new kernels.
> /* unknown reason for SCX being preempted */
> SCX_CPU_PREEMPT_UNKNOWN,
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260612152304.94821-1-cjian720@163.com?part=1
next prev parent reply other threads:[~2026-06-12 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 15:23 [PATCH] sched_ext:SCX is preemptible by the Fair scheduler Cui Jian
2026-06-12 15:38 ` sashiko-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-12 16:14 Cui Jian
2026-06-12 16:28 ` sashiko-bot
2026-06-12 16:32 ` Andrea Righi
2026-06-12 17:51 Cui Jian
2026-06-12 18:00 ` Andrea Righi
2026-06-12 18:05 ` 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=20260612153843.302E81F000E9@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 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.