[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130912201717.GX3966@linux.vnet.ibm.com>
Date: Thu, 12 Sep 2013 13:17:17 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Mike Travis <travis@....com>,
Peter Zijlstra <peterz@...radead.org>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Jason Wessel <jason.wessel@...driver.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Dimitri Sivanich <sivanich@....com>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 9/9] x86/UV: Add ability to disable UV NMI handler
On Thu, Sep 12, 2013 at 08:48:33PM +0100, Hedi Berriche wrote:
> On Thu, Sep 12, 2013 at 19:59 Mike Travis wrote:
> | On 9/12/2013 10:27 AM, Paul E. McKenney wrote:
> |
> | > But what is it that you are looking for? If you want to silence it
> | > completely, the rcu_cpu_stall_suppress boot/sysfs parameter is what
> | > you want to use.
> |
> | We have by default rcutree.rcu_cpu_stall_suppress=1 on the kernel
> | cmdline. I'll double check if it was set during my testing.
>
> FWIW, for recent enough kernels the correct boot parameter is
> rcupdate.rcu_cpu_stall_suppress.
>
> It used to be rcutree.rcu_cpu_stall_suppress, but that has changed after
> commit 6bfc09e.
Good point, Hedi! That change happened when rcutiny gained RCU CPU
stall warning capability.
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