[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210412102001.224578981@infradead.org>
Date: Mon, 12 Apr 2021 12:14:24 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: mingo@...nel.org, mgorman@...e.de, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, bristot@...hat.com,
joshdon@...gle.com, valentin.schneider@....com
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org, greg@...ah.com,
linux@...musvillemoes.dk
Subject: [PATCH v2 3/9] sched: Dont make LATENCYTOP select SCHED_DEBUG
SCHED_DEBUG is not in fact required for LATENCYTOP, don't select it.
Suggested-by: Mel Gorman <mgorman@...e.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.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.
Powered by blists - more mailing lists