Message ID | 20130623133928.19094.8259.stgit@srivatsabhat.in.ibm.com (mailing list archive) |
---|---|
State | Not Applicable, archived |
Headers | show |
Hello. On 23-06-2013 17:39, Srivatsa S. Bhat wrote: > 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 <akpm@linux-foundation.org> > Cc: "Paul E. McKenney" <paul.mckenney@linaro.org> > Cc: Akinobu Mita <akinobu.mita@gmail.com> > Cc: Catalin Marinas <catalin.marinas@arm.com> > Cc: Michel Lespinasse <walken@google.com> > Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> > --- > lib/Kconfig.debug | 9 +++++++++ > 1 file changed, 9 insertions(+) > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index 566cf2b..6be1e72 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -512,6 +512,15 @@ 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 > + default n It's the default default, no need to specify it. WBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 06/23/2013 08:38 PM, Sergei Shtylyov wrote: > Hello. > > On 23-06-2013 17:39, Srivatsa S. Bhat wrote: > >> 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 <akpm@linux-foundation.org> >> Cc: "Paul E. McKenney" <paul.mckenney@linaro.org> >> Cc: Akinobu Mita <akinobu.mita@gmail.com> >> Cc: Catalin Marinas <catalin.marinas@arm.com> >> Cc: Michel Lespinasse <walken@google.com> >> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> >> --- > >> lib/Kconfig.debug | 9 +++++++++ >> 1 file changed, 9 insertions(+) > >> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug >> index 566cf2b..6be1e72 100644 >> --- a/lib/Kconfig.debug >> +++ b/lib/Kconfig.debug >> @@ -512,6 +512,15 @@ 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 >> + default n > > It's the default default, no need to specify it. > Ah, I see. Thanks! Regards, Srivatsa S. Bhat -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 566cf2b..6be1e72 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -512,6 +512,15 @@ 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 + default n + 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
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 <akpm@linux-foundation.org> Cc: "Paul E. McKenney" <paul.mckenney@linaro.org> Cc: Akinobu Mita <akinobu.mita@gmail.com> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Michel Lespinasse <walken@google.com> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> --- lib/Kconfig.debug | 9 +++++++++ 1 file changed, 9 insertions(+) -- To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html