From: Zhao Mengmeng <zhaomzhao@126.com>
To: tj@kernel.org, void@manifault.com, arighi@nvidia.com,
changwoo@igalia.com
Cc: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
zhaomengmeng@kylinos.cn
Subject: [PATCH 1/2] tools/sched_ext: Add missing -c option in scx_qmap help
Date: Wed, 15 Apr 2026 17:54:17 +0800 [thread overview]
Message-ID: <20260415095418.307555-2-zhaomzhao@126.com> (raw)
In-Reply-To: <20260415095418.307555-1-zhaomzhao@126.com>
From: Zhao Mengmeng <zhaomengmeng@kylinos.cn>
The sub-scheduler api has been added to scx_qmap, but the new -c option is
missing in help, which is hard to understand and use. Add it in help.
Signed-off-by: Zhao Mengmeng <zhaomengmeng@kylinos.cn>
---
tools/sched_ext/scx_qmap.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/sched_ext/scx_qmap.c b/tools/sched_ext/scx_qmap.c
index e7c89a2bc3d8..b5fce6dcee14 100644
--- a/tools/sched_ext/scx_qmap.c
+++ b/tools/sched_ext/scx_qmap.c
@@ -32,6 +32,7 @@ const char help_fmt[] =
" -P Print out DSQ content and event counters to trace_pipe every second\n"
" -M Print out debug messages to trace_pipe\n"
" -H Boost nice -20 tasks in SHARED_DSQ, use with -b\n"
+" -c CG_PATH Cgroup path to attach as sub-scheduler, must run parent scheduler first\n"
" -d PID Disallow a process from switching into SCHED_EXT (-1 for self)\n"
" -D LEN Set scx_exit_info.dump buffer length\n"
" -S Suppress qmap-specific debug dump\n"
--
2.43.0
next prev parent reply other threads:[~2026-04-15 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 9:54 [PATCH 0/2] sched_ext: Cgroup sub-scheduler minor fixes Zhao Mengmeng
2026-04-15 9:54 ` Zhao Mengmeng [this message]
2026-04-15 10:46 ` [PATCH 1/2] tools/sched_ext: Add missing -c option in scx_qmap help Cheng-Yang Chou
2026-04-15 10:48 ` Zhao mengmeng
2026-04-15 9:54 ` [PATCH 2/2] sched_ext: Print sub-scheduler disabled log and reason Zhao Mengmeng
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=20260415095418.307555-2-zhaomzhao@126.com \
--to=zhaomzhao@126.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--cc=zhaomengmeng@kylinos.cn \
/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
all inboxes | Powered by JetHome®