Remove the "single task" statement from CONFIG_NO_HZ_FULL
title. The constraint can be invalidated when tasks from
other sched classes than SCHED_FAIR are running. Moreover
it's possible that hrtick join the party in the future.

Also add a line about the dependency on SMP.

Reported-by: Ingo Molnar <mi...@kernel.org>
Signed-off-by: Frederic Weisbecker <fweis...@gmail.com>
Cc: Chris Metcalf <cmetc...@tilera.com>
Cc: Christoph Lameter <c...@linux.com>
Cc: Geoff Levand <ge...@infradead.org>
Cc: Gilad Ben Yossef <gi...@benyossef.com>
Cc: Hakan Akkan <hakanak...@gmail.com>
Cc: Ingo Molnar <mi...@kernel.org>
Cc: Kevin Hilman <khil...@linaro.org>
Cc: Li Zhong <zh...@linux.vnet.ibm.com>
Cc: Paul E. McKenney <paul...@linux.vnet.ibm.com>
Cc: Paul Gortmaker <paul.gortma...@windriver.com>
Cc: Peter Zijlstra <pet...@infradead.org>
Cc: Steven Rostedt <rost...@goodmis.org>
Cc: Thomas Gleixner <t...@linutronix.de>
---
 kernel/time/Kconfig |    8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/kernel/time/Kconfig b/kernel/time/Kconfig
index 3b68322..358d601 100644
--- a/kernel/time/Kconfig
+++ b/kernel/time/Kconfig
@@ -97,11 +97,13 @@ config NO_HZ_IDLE
          Most of the time you want to say Y here.
 
 config NO_HZ_FULL
-       bool "Full dynticks system (tickless single task)"
+       bool "Full dynticks system (tickless)"
        # NO_HZ_COMMON dependency
        depends on !ARCH_USES_GETTIMEOFFSET && GENERIC_CLOCKEVENTS
-       # RCU_USER_QS
-       depends on HAVE_CONTEXT_TRACKING && SMP
+       # We need at least one periodic CPU for timekeeping
+       depends on SMP
+       # RCU_USER_QS dependency
+       depends on HAVE_CONTEXT_TRACKING
        # RCU_NOCB_CPU dependency
        depends on TREE_RCU || TREE_PREEMPT_RCU
        depends on VIRT_CPU_ACCOUNTING_GEN
-- 
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to