sched/isolation: Enable CONFIG_CPU_ISOLATION=y by default

The "isolcpus=" boot parameter support was always built-in before we
moved the related code under CONFIG_CPU_ISOLATION. Having it disabled by
default is very confusing for people accustomed to use this parameter.

So enable it by dafault to keep the previous behaviour but keep it
optable for those who want to tinify their kernels.

Signed-off-by: Frederic Weisbecker <[e-mail]>
Cc: Chris Metcalf <[e-mail]>
Cc: Christoph Lameter <[e-mail]>
Cc: John Stultz <[e-mail]>
Cc: Linus Torvalds <[e-mail]>
Cc: Luiz Capitulino <[e-mail]>
Cc: Mike Galbraith <[e-mail]>
Cc: Paul E. McKenney <[e-mail]>
Cc: Peter Zijlstra <[e-mail]>
Cc: Rik van Riel <[e-mail]>
Cc: Thomas Gleixner <[e-mail]>
Cc: Wanpeng Li <[e-mail]>
Cc: kernel test robot <[e-mail]>
Link: http://lkml.kernel.org/r/[e-mail]
Signed-off-by: Ingo Molnar <[e-mail]>

init/Kconfig

···
 
 config CPU_ISOLATION
 	bool "CPU isolation"
+	default y
 	help
 	  Make sure that CPUs running critical tasks are not disturbed by
 	  any source of "noise" such as unbound workqueues, timers, kthreads...
-	  Unbound jobs get offloaded to housekeeping CPUs.
+	  Unbound jobs get offloaded to housekeeping CPUs. This is driven by
+	  the "isolcpus=" boot parameter.
+
+	  Say Y if unsure.
 
 source "kernel/rcu/Kconfig"