Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751607AbZJTJVW (ORCPT ); Tue, 20 Oct 2009 05:21:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751580AbZJTJVW (ORCPT ); Tue, 20 Oct 2009 05:21:22 -0400 Received: from casper.infradead.org ([85.118.1.10]:57018 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751516AbZJTJVV (ORCPT ); Tue, 20 Oct 2009 05:21:21 -0400 Subject: Re: Commit 34d76c41 causes linker errors on ia64 with NR_CPUS=4096 From: Peter Zijlstra To: Ingo Molnar Cc: Jiri Kosina , Jeff Mahoney , Linux Kernel Mailing List , Tony Luck , Fenghua Yu , linux-ia64@vger.kernel.org In-Reply-To: <20091020061557.GE8550@elte.hu> References: <4ADB967A.4080707@suse.com> <20091020061557.GE8550@elte.hu> Content-Type: text/plain Date: Tue, 20 Oct 2009 11:21:14 +0200 Message-Id: <1256030474.17774.36.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 650 Lines: 16 On Tue, 2009-10-20 at 08:15 +0200, Ingo Molnar wrote: > > Seems like an IA64 bug to me. It's _very_ easy to get more than 64K of > percpu data - i'm wondering why IA64 only triggered it now? Sure > lockdep/lockstat must have triggered it before. I seem to remember people wanting to make lockstat data dynamically allocated because of this. But then, I'm not sure ia64 actually has lockdep support. -- 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/