From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by ozlabs.org (Postfix) with ESMTP id E4F1967A03 for ; Mon, 3 Apr 2006 15:25:21 +1000 (EST) Date: Sun, 2 Apr 2006 22:25:16 -0700 (PDT) From: Christoph Lameter To: Paul Jackson Subject: Re: Fw: 2.6.16 crashes when running numastat on p575 In-Reply-To: <20060402221513.96f05bdc.pj@sgi.com> Message-ID: References: <20060402213216.2e61b74e.akpm@osdl.org> <20060402221513.96f05bdc.pj@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Christoph Lameter Cc: akpm@osdl.org, linuxppc-dev@ozlabs.org, ak@suse.com, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, 2 Apr 2006, Paul Jackson wrote: > - for (cpu = 0; cpu < NR_CPUS; cpu++) { > + for_each_online_cpu(cpu) { > > Idle curiosity -- what keeps a cpu from going offline during > this scan, and leaving us with the same crash as before? Nothing keeps a processor from going offline. We could take the hotplug lock for every for_each_online_cpu() in the kernel. Could you take that up with the hotplug folks?