From: Tejun Heo <tj@kernel.org>
To: Zqiang <qiang.zhang@linux.dev>
Cc: void@manifault.com, arighi@nvidia.com, changwoo@igalia.com,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Choose the right sch->ops.name to output in the print_scx_info()
Date: Tue, 24 Mar 2026 04:37:34 -1000 [thread overview]
Message-ID: <acKhrjVIHe08UA0j@slm.duckdns.org> (raw)
In-Reply-To: <20260324120313.12632-1-qiang.zhang@linux.dev>
On Tue, Mar 24, 2026 at 08:03:13PM +0800, Zqiang wrote:
> This commit use the scx_task_sched_rcu() to get task->scx.sched
"This commit uses", but that just do imperative - "Use the...".
> structure to correctly output, instead of always using scx_root
> in the print_scx_info().
>
> Signed-off-by: Zqiang <qiang.zhang@linux.dev>
> ---
> kernel/sched/ext.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
> index 2472231ec556..5d670b50da3d 100644
> --- a/kernel/sched/ext.c
> +++ b/kernel/sched/ext.c
> @@ -7680,14 +7680,18 @@ static void kick_cpus_irq_workfn(struct irq_work *irq_work)
> */
> void print_scx_info(const char *log_lvl, struct task_struct *p)
> {
> - struct scx_sched *sch = scx_root;
> + struct scx_sched *sch;
> enum scx_enable_state state = scx_enable_state();
> const char *all = READ_ONCE(scx_switching_all) ? "+all" : "";
> char runnable_at_buf[22] = "?";
> struct sched_class *class;
> unsigned long runnable_at;
>
> - if (state == SCX_DISABLED)
> + guard(rcu)();
> +
> + sch = scx_task_sched_rcu(p);
> +
> + if (!sch || state == SCX_DISABLED)
I think you can drop the state test w/ scx_task_sched_rcu() usage.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-03-24 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 12:03 [PATCH] sched_ext: Choose the right sch->ops.name to output in the print_scx_info() Zqiang
2026-03-24 14:37 ` Tejun Heo [this message]
2026-03-26 6:28 ` kernel test robot
2026-03-26 6:42 ` kernel test robot
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=acKhrjVIHe08UA0j@slm.duckdns.org \
--to=tj@kernel.org \
--cc=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=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