Now that we have all the pieces of the CPU hotplug debug infrastructure
in place, expose the feature by growing a new Kconfig option,
CONFIG_DEBUG_HOTPLUG_CPU.

Cc: Andrew Morton <a...@linux-foundation.org>
Cc: "Paul E. McKenney" <paul.mcken...@linaro.org>
Cc: Akinobu Mita <akinobu.m...@gmail.com>
Cc: Catalin Marinas <catalin.mari...@arm.com>
Cc: Michel Lespinasse <wal...@google.com>
Cc: Sergei Shtylyov <sergei.shtyl...@cogentembedded.com>
Signed-off-by: Srivatsa S. Bhat <srivatsa.b...@linux.vnet.ibm.com>
---

 lib/Kconfig.debug |    8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 7154f79..42e17f0 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -512,6 +512,14 @@ config DEBUG_PREEMPT
          if kernel code uses it in a preemption-unsafe way. Also, the kernel
          will detect preemption count underflows.
 
+config DEBUG_HOTPLUG_CPU
+       bool "Debug CPU hotplug"
+       depends on HOTPLUG_CPU
+       help
+         If you say Y here, the kernel will check all the accesses of
+         cpu_online_mask from atomic contexts, and will print warnings if
+         the task lacks appropriate synchronization with CPU hotplug.
+
 config DEBUG_RT_MUTEXES
        bool "RT Mutex debugging, deadlock detection"
        depends on DEBUG_KERNEL && RT_MUTEXES

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to