From: Andrea Righi <arighi@nvidia.com>
To: Zicheng Qu <quzicheng315@gmail.com>
Cc: tj@kernel.org, void@manifault.com, changwoo@igalia.com,
enjuk@amazon.com, emil@etsalapatis.com,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
tanghui20@huawei.com, zhangqiao22@huawei.com,
quzicheng@huawei.com
Subject: Re: [PATCH] tools/sched_ext: Fix scx_show_state per-scheduler state reads
Date: Tue, 26 May 2026 19:44:35 +0200 [thread overview]
Message-ID: <ahXcAzxZbw6g_dLO@gpd4> (raw)
In-Reply-To: <20260526135123.1892092-1-quzicheng315@gmail.com>
Hi Zicheng,
On Tue, May 26, 2026 at 09:51:23PM +0800, Zicheng Qu wrote:
> From: Zicheng Qu <quzicheng@huawei.com>
>
> scx_show_state.py still reads scx_aborting and scx_bypass_depth as
> global symbols. Those symbols no longer exist after the state was moved
> into struct scx_sched, so the drgn script fails when it reaches either
> field.
>
> Fixes: 5c8d98a1b4de ("sched_ext: Move bypass state into scx_sched")
> Fixes: c1743da43cf5 ("sched_ext: Move aborting flag to per-scheduler field")
> Signed-off-by: Zicheng Qu <quzicheng@huawei.com>
Makes sense to me.
Let's keep in mind that with the sub-scheduler support the script will only
report aborting and bypass_depth only from scx_root (not the sub-scheds). Maybe
we should mention this in the patch description, but the patch looks good.
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Thanks,
-Andrea
> ---
> tools/sched_ext/scx_show_state.py | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/tools/sched_ext/scx_show_state.py b/tools/sched_ext/scx_show_state.py
> index 02e43c184d43..446d82807f90 100644
> --- a/tools/sched_ext/scx_show_state.py
> +++ b/tools/sched_ext/scx_show_state.py
> @@ -27,18 +27,25 @@ def read_static_key(name):
> def state_str(state):
> return prog['scx_enable_state_str'][state].string_().decode()
>
> +def read_root_ops_name():
> + if root:
> + return root.ops.name.string_().decode()
> + return ''
> +
> +def read_root_field(name, default):
> + if root:
> + return getattr(root, name).value_()
> + return default
> +
> root = prog['scx_root']
> enable_state = read_atomic("scx_enable_state_var")
>
> -if root:
> - print(f'ops : {root.ops.name.string_().decode()}')
> -else:
> - print('ops : ')
> +print(f'ops : {read_root_ops_name()}')
> print(f'enabled : {read_static_key("__scx_enabled")}')
> print(f'switching_all : {read_int("scx_switching_all")}')
> print(f'switched_all : {read_static_key("__scx_switched_all")}')
> print(f'enable_state : {state_str(enable_state)} ({enable_state})')
> -print(f'aborting : {prog["scx_aborting"].value_()}')
> -print(f'bypass_depth : {prog["scx_bypass_depth"].value_()}')
> +print(f'aborting : {read_root_field("aborting", False)}')
> +print(f'bypass_depth : {read_root_field("bypass_depth", 0)}')
> print(f'nr_rejected : {read_atomic("scx_nr_rejected")}')
> print(f'enable_seq : {read_atomic("scx_enable_seq")}')
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-05-26 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 13:51 [PATCH] tools/sched_ext: Fix scx_show_state per-scheduler state reads Zicheng Qu
2026-05-26 17:44 ` Andrea Righi [this message]
2026-05-27 9:38 ` [PATCH v2] " quzicheng315
2026-05-27 19:16 ` 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=ahXcAzxZbw6g_dLO@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=emil@etsalapatis.com \
--cc=enjuk@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quzicheng315@gmail.com \
--cc=quzicheng@huawei.com \
--cc=sched-ext@lists.linux.dev \
--cc=tanghui20@huawei.com \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--cc=zhangqiao22@huawei.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.