[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150513094648.72e03399@gandalf.local.home>
Date: Wed, 13 May 2015 09:46:48 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com,
fweisbec@...il.com, oleg@...hat.com, bobby.prani@...il.com
Subject: Re: [PATCH tip/core/rcu 24/24] rcu: Conditionally compile RCU's eqs
warnings
On Tue, 12 May 2015 15:30:54 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1373,6 +1373,17 @@ config RCU_TRACE
> Say Y here if you want to enable RCU tracing
> Say N if you are unsure.
>
> +config RCU_EQS_DEBUG
> + bool "Use this when adding any sort of NO_HZ support to your arch"
> + depends on DEBUG_KERNEL
Should we add "depends on NO_HZ" ?
-- Steve
> + help
> + This option provides consistency checks in RCU's handling of
> + NO_HZ. These checks have proven quite helpful in detecting
> + bugs in arch-specific NO_HZ code.
> +
> + Say N here if you need ultimate kernel/user switch latencies
> + Say Y if you are unsure
> +
> endmenu # "RCU Debugging"
>
> config DEBUG_BLOCK_EXT_DEVT
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists