From: Peter Zijlstra <peterz@infradead.org>
To: mingo@kernel.org, mgorman@suse.de, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, bristot@redhat.com,
joshdon@google.com, valentin.schneider@arm.com
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, greg@kroah.com
Subject: [PATCH 3/9] sched: Dont make LATENCYTOP select SCHED_DEBUG
Date: Fri, 26 Mar 2021 11:33:55 +0100 [thread overview]
Message-ID: <20210326103934.946702998@infradead.org> (raw)
In-Reply-To: 20210326103352.603456266@infradead.org
SCHED_DEBUG is not in fact required for LATENCYTOP, don't select it.
Suggested-by: Mel Gorman <mgorman@suse.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
lib/Kconfig.debug | 1 -
1 file changed, 1 deletion(-)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1670,7 +1670,6 @@ config LATENCYTOP
select KALLSYMS_ALL
select STACKTRACE
select SCHEDSTATS
- select SCHED_DEBUG
help
Enable this option if you want to use the LatencyTOP tool
to find out which userspace is blocking on what kernel operations.
next prev parent reply other threads:[~2021-03-26 10:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 10:33 [PATCH 0/9] sched: Clean up SCHED_DEBUG Peter Zijlstra
2021-03-26 10:33 ` [PATCH 1/9] sched/numa: Allow runtime enabling/disabling of NUMA balance without SCHED_DEBUG Peter Zijlstra
2021-03-26 10:33 ` [PATCH 2/9] sched: Remove sched_schedstats sysctl out from under SCHED_DEBUG Peter Zijlstra
2021-03-26 10:33 ` Peter Zijlstra [this message]
2021-03-26 10:33 ` [PATCH 4/9] sched: Move SCHED_DEBUG to debugfs Peter Zijlstra
2021-03-26 11:06 ` Greg KH
2021-04-07 10:46 ` Valentin Schneider
2021-04-07 12:26 ` Peter Zijlstra
2021-04-07 12:57 ` Valentin Schneider
2021-03-26 10:33 ` [PATCH 5/9] sched,preempt: Move preempt_dynamic to debug.c Peter Zijlstra
2021-03-26 10:33 ` [PATCH 6/9] debugfs: Implement debugfs_create_str() Peter Zijlstra
2021-03-26 11:05 ` Greg KH
2021-03-26 11:18 ` Peter Zijlstra
2021-03-26 11:30 ` Greg KH
2021-03-26 11:38 ` [PATCH v2 " Peter Zijlstra
2021-03-26 12:18 ` Greg KH
2021-03-26 12:53 ` Rasmus Villemoes
2021-03-26 12:57 ` Greg KH
2021-03-26 13:10 ` Rasmus Villemoes
2021-03-26 14:12 ` Peter Zijlstra
2021-03-26 14:19 ` Greg KH
2021-03-26 14:22 ` Peter Zijlstra
2021-03-26 14:58 ` Rasmus Villemoes
2021-03-26 15:19 ` Peter Zijlstra
2021-03-27 10:41 ` Greg KH
2021-03-26 14:50 ` [PATCH v3 " Peter Zijlstra
2021-03-27 10:42 ` Greg KH
2021-03-27 22:24 ` [PATCH " Al Viro
2021-03-28 0:33 ` Steven Rostedt
2021-03-26 10:33 ` [PATCH 7/9] sched,debug: Convert sysctl sched_domains to debugfs Peter Zijlstra
2021-03-26 13:11 ` Dietmar Eggemann
2021-04-07 10:46 ` Valentin Schneider
2021-04-07 12:18 ` Peter Zijlstra
2021-03-26 10:34 ` [PATCH 8/9] sched: Move /proc/sched_debug " Peter Zijlstra
2021-03-26 11:05 ` Greg KH
2021-03-26 10:34 ` [PATCH 9/9] sched,fair: Alternative sched_slice() Peter Zijlstra
2021-03-26 12:08 ` Dietmar Eggemann
2021-03-26 14:07 ` Peter Zijlstra
2021-03-26 15:37 ` Vincent Guittot
2021-03-26 18:30 ` Peter Zijlstra
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=20210326103934.946702998@infradead.org \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=greg@kroah.com \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
/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).