Your X86_GENERIC is semantically equivalent to M386.
> @@ -288,10 +295,10 @@
>
> config X86_L1_CACHE_SHIFT
> int
> + default "7" if MPENTIUM4 || X86_GENERIC
> default "4" if MELAN || M486 || M386
> default "5" if MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCRUSOE || MCYRIXIII || MK6 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || M586 || MVIAC3_2
> default "6" if MK7 || MK8
> - default "7" if MPENTIUM4
>
> config RWSEM_GENERIC_SPINLOCK
> bool
This doesn't work. E.g. MPENTIUMIII has the semantics of "support
Pentium-III and above". If you want to compile a kernel that runs on
both a Pentium-III and a Pentium-4 you choose MPENTIUMIII which implies
X86_L1_CACHE_SHIFT=5 ...
I'm currently working on changing the "Processor family" options from
the current "select the minimum processor you want to support" to
"select all processors you want to support:
[ ] 386
[ ] 486
...
[ ] VIA C3-2"
with the possibility to select one or more processors from the list.
X86_L1_CACHE_SHIFT will simply work with the following (using the
Kconfig feature that the first "default" with fulfilled "if" is used):
config X86_L1_CACHE_SHIFT
int
default "7" if MPENTIUM4
default "6" if MK7 || MK8
default "5" if MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCRUSOE || MCYRIXIII || MK6 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || M586 || MVIAC3_2
default "4" if MELAN || M486 || M386
Additionally this will make it possible to solve cases where users
configuring the kernel currently ask "Which CPU should I select for a
kernel that runs on both a K6 and a Pentium-III?" automatically inside
arch/i386/Makefile.
I'll send a patch within the next days.
cu
Adrian
--"Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
- 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/