On Wed, 2006-04-12 at 10:01 -0700, Raj, Ashok wrote: > > > >Okay, what is "tiger defconfig"? I'm also unfamiliar with what bsp > >removal is -- is that a hp memory feature for ia64? > > Tiger_defconfig is golden config that works on tiger4 systems. if you > are compiling for tiger, you could use make tiger_defconfig, to generate > your .config, and then build. > > BSP removal is support to remove cpu0, (BootStrap Processor) On > i386/x86_64 cpu0 removal is prohibited (for now), ia64 and I think ppc64 > also supports ability to remove cpu0. Ashok (or anyone out there), Is there a universal way to tell (from a test script) whether or not the particular system you are running allows cpu0 to be off-lined (other than to try it) ? I ask because we could check that it works in our regression tests, _if we know it is _supposed to work. But without knowing, when a cpu0 does not offline, we have to assume that is as intended. If there is no universal way, would there likely be a way for each architecture to tell from a script? TIA -- Mary Edie Meredith Initiative Manager Open Source Development Labs maryedie@xxxxxxxx 503-906-1942
