From: Barry Song <song.bao.hua@hisilicon.com>
To: <corbet@lwn.net>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <linuxarm@huawei.com>,
Valentin Schneider <valentin.schneider@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Mel Gorman" <mgorman@suse.de>, Adrian Freund <adrian@freund.io>,
Barry Song <song.bao.hua@hisilicon.com>
Subject: [PATCH v2 2/2] Documentation: scheduler: ask users to set sched_debug cmdline
Date: Fri, 13 Nov 2020 11:31:29 +1300 [thread overview]
Message-ID: <20201112223129.26580-2-song.bao.hua@hisilicon.com> (raw)
In-Reply-To: <20201112223129.26580-1-song.bao.hua@hisilicon.com>
From: Valentin Schneider <valentin.schneider@arm.com>
To print the schedule debug information, users need to set sched_debug
cmdline or enable it by sysfs entry.
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Mel Gorman <mgorman@suse.de>
Cc: Adrian Freund <adrian@freund.io>
Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
Signed-off-by: Barry Song <song.bao.hua@hisilicon.com>
---
Documentation/scheduler/sched-domains.rst | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/Documentation/scheduler/sched-domains.rst b/Documentation/scheduler/sched-domains.rst
index 55983b7e1098..8582fa5e9170 100644
--- a/Documentation/scheduler/sched-domains.rst
+++ b/Documentation/scheduler/sched-domains.rst
@@ -74,6 +74,8 @@ for a given topology level by creating a sched_domain_topology_level array and
calling set_sched_topology() with this array as the parameter.
The sched-domains debugging infrastructure can be enabled by enabling
-CONFIG_SCHED_DEBUG. This enables an error checking parse of the sched domains
-which should catch most possible errors (described above). It also prints out
-the domain structure in a visual format.
+CONFIG_SCHED_DEBUG and adding 'sched_debug' to your cmdline. If you forgot to
+tweak your cmdline, you can also flip the /sys/kernel/debug/sched_debug
+knob. This enables an error checking parse of the sched domains which should
+catch most possible errors (described above). It also prints out the domain
+structure in a visual format.
--
2.25.1
next prev parent reply other threads:[~2020-11-12 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 22:31 [PATCH v2 1/2] Documentation: scheduler: fix outdated information on arch SD flags and sched_domain Barry Song
2020-11-12 22:31 ` Barry Song [this message]
2020-11-13 11:34 ` [PATCH v2 2/2] Documentation: scheduler: ask users to set sched_debug cmdline Valentin Schneider
2020-11-13 11:41 ` Song Bao Hua (Barry Song)
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=20201112223129.26580-2-song.bao.hua@hisilicon.com \
--to=song.bao.hua@hisilicon.com \
--cc=adrian@freund.io \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.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;
as well as URLs for NNTP newsgroup(s).