Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761987AbYFDS4N (ORCPT ); Wed, 4 Jun 2008 14:56:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757490AbYFDSz5 (ORCPT ); Wed, 4 Jun 2008 14:55:57 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:55690 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754015AbYFDSz4 (ORCPT ); Wed, 4 Jun 2008 14:55:56 -0400 Subject: Re: Stop machine threads are getting preemted by the rt period enforcement From: Peter Zijlstra To: Max Krasnyansky Cc: Dimitri Sivanich , linux-kernel@vger.kernel.org, Ingo Molnar , Nick Piggin , rostedt@goodmis.org, Oleg Nesterov , "Paul E. McKenney" , Paul Menage , "Randy.Dunlap" , suresh.b.siddha@intel.com In-Reply-To: <4846DDC1.1050203@qualcomm.com> References: <20080601213019.14ea8ef8.pj@sgi.com> <20080602164203.GA2477@sgi.com> <48443E66.6060205@qualcomm.com> <20080602214151.GA7072@sgi.com> <48446D46.2010903@qualcomm.com> <20080603144010.GA25948@sgi.com> <20080604140036.GC18993@sgi.com> <4846D9FE.4030804@qualcomm.com> <1212603506.19205.2.camel@lappy.programming.kicks-ass.net> <4846DDC1.1050203@qualcomm.com> Content-Type: text/plain Date: Wed, 04 Jun 2008 20:55:25 +0200 Message-Id: <1212605725.19205.17.camel@lappy.programming.kicks-ass.net> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1065 Lines: 29 On Wed, 2008-06-04 at 11:24 -0700, Max Krasnyansky wrote: > > Peter Zijlstra wrote: > > On Wed, 2008-06-04 at 11:07 -0700, Max Krasnyansky wrote: > >> Peter, Ingo, > >> > >> Take a look at the report below (came up during isolcpu= remove discussions). > >> > >> It looks like stop_machine threads are getting forcefully preempted because > >> they exceed their RT quanta. It's strange because rt period is pretty long. > >> But given that disabling rt period logic solves the issue the machine was not > >> really stuck. > > > > Yeah, I know, I'm already looking at this > > I see. Does it look like a bug in the rt period logic ? > Or did the stop_machine thread really run for a long time (in the report that > you got that is) ? looks like a fun race between refreshing the period and updating cpu_online_map. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/