From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752674Ab2IVSmK (ORCPT ); Sat, 22 Sep 2012 14:42:10 -0400 Received: from utopia.booyaka.com ([74.50.51.50]:36192 "EHLO utopia.booyaka.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751828Ab2IVSmJ (ORCPT ); Sat, 22 Sep 2012 14:42:09 -0400 Date: Sat, 22 Sep 2012 18:42:08 +0000 (UTC) From: Paul Walmsley To: "Paul E. McKenney" cc: "Bruce, Becky" , "Paul E. McKenney" , "" , "" , "" , "Hilman, Kevin" , "Shilimkar, Santosh" , "Hunter, Jon" , "" , fweisbec@gmail.com Subject: Re: rcu self-detected stall messages on OMAP3, 4 boards In-Reply-To: <20120921195717.GD2454@linux.vnet.ibm.com> Message-ID: References: <20120920000351.GI2455@linux.vnet.ibm.com> <20120920220130.GN2449@linux.vnet.ibm.com> <20120920232114.GO2449@linux.vnet.ibm.com> <20120921185827.GC2454@linux.vnet.ibm.com> <20120921195717.GD2454@linux.vnet.ibm.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 21 Sep 2012, Paul E. McKenney wrote: > Could you please point me to a recipe for creating a minimal userspace? > Just in case it is the userspac erather than the architecture/hardware > that makes the difference. Tony's suggestion is pretty good. Note that there may also be differences in kernel timers -- either between x86 and ARM architectures, or loaded device drivers -- that may confound the problem. > Just to make sure I understand the combinations: > > o All stalls have happened when running a minimal userspace. > o CONFIG_NO_HZ=n suppresses the stalls. > o CONFIG_RCU_FAST_NO_HZ (which depends on CONFIG_NO_HZ=y) has > no observable effect on the stalls. > > Did I get that right, or am I missing a combination? That's correct. > Indeed, rcu_idle_gp_timer_func() is a bit strange in that it is > cancelled upon exit from idle, and therefore should (almost) never > actually execute. Its sole purpose is to wake up the CPU. ;-) Right. Just curious, what would wake up the kernel from idle to handle a grace period expiration when CONFIG_RCU_FAST_NO_HZ=n? On a very idle system, the time between timer ticks could potentially be several tens of seconds. - Paul