Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932717AbWAFShp (ORCPT ); Fri, 6 Jan 2006 13:37:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932718AbWAFSho (ORCPT ); Fri, 6 Jan 2006 13:37:44 -0500 Received: from omx2-ext.sgi.com ([192.48.171.19]:10477 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S932717AbWAFShn (ORCPT ); Fri, 6 Jan 2006 13:37:43 -0500 Date: Fri, 6 Jan 2006 10:37:33 -0800 (PST) From: Christoph Lameter To: "Randy.Dunlap" cc: Matthew Wilcox , "Luck, Tony" , Arjan van de Ven , hawkes@sgi.com, Tony Luck , Andrew Morton , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, Jack Steiner , Dan Higgins , John Hesterberg , Greg Edwards Subject: Re: [PATCH] ia64: change defconfig to NR_CPUS==1024 In-Reply-To: Message-ID: References: <20060106174957.GF19769@parisc-linux.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 959 Lines: 23 On Fri, 6 Jan 2006, Randy.Dunlap wrote: > > The dicey thing in all of this is that the generic kernels will be used > > for the certification of applications. If the cpu limit is too low then > > applications will simply not be certified for these high processor counts. > > One may encounter problems if the app is then run with a higher processor > > count. > > Do you equate a 'defconfig' kernel with a generic kernel? > > I would expect certs to be done on vendor kernels, and as > Arjan has suggested, they will have their own configs, > not defconfig. Vendors look for the upstream defaults and orient themselves on the defconfig. It is best to have as much common code and configurations as possible. - 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/