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 <[email protected]>
Cc: "Paul E. McKenney" <[email protected]>
Cc: Akinobu Mita <[email protected]>
Cc: Catalin Marinas <[email protected]>
Cc: Michel Lespinasse <[email protected]>
Cc: Sergei Shtylyov <[email protected]>
Signed-off-by: Srivatsa S. Bhat <[email protected]>
---

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

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 566cf2b..ec6be74 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
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