Messages in this thread |  | | | Date | Fri, 6 Jan 2006 16:00:24 -0500 | | From | Dave Jones <> | | Subject | Re: [PATCH] ia64: change defconfig to NR_CPUS==1024 |
| |
On Fri, Jan 06, 2006 at 10:37:33AM -0800, Christoph Lameter wrote: > 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.
As someone who builds vendor kernels, I can say this isn't true (from my experience at least). When a new config option appears, I look at the Kconfig, and make a decision. I *never* even look at the defconfig, as a lot of the time, they are either out of date, or irrelevant.
Dave
- 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/
|  |