[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150730151341.GD27280@linux.vnet.ibm.com>
Date: Thu, 30 Jul 2015 08:13:41 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
jiangshanlai@...il.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, rostedt@...dmis.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 02/19] rcu: Remove CONFIG_RCU_CPU_STALL_INFO
On Thu, Jul 30, 2015 at 02:49:55PM +0200, Peter Zijlstra wrote:
> On Fri, Jul 17, 2015 at 04:29:07PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
> >
> > The CONFIG_RCU_CPU_STALL_INFO has been default-y for a couple of
> > releases with no complaints, so it is time to eliminate this Kconfig
> > option entirely, so that the long-form RCU CPU stall warnings cannot
> > be disabled. This commit does just that.
>
> I would think the tiny people (/me looks @ Josh) would complain about
> this..
They might, but if they do, I will point out that CONFIG_RCU_CPU_STALL_INFO
only has effect for Tree RCU. And also that RCU CPU stall warnings are
compiled out unless CONFIG_RCU_TRACE=y, which I suspect they are disabling.
All that aside, I do appreciate the attention to tininess.
Thanx, Paul
--
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