[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
# Put here option for CPU selection and depending optimization
|
|
|
|
if !X86_ELAN
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Processor family"
|
2007-11-06 13:35:08 -07:00
|
|
|
default M686 if X86_32
|
|
|
|
default GENERIC_CPU if X86_64
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config M386
|
|
|
|
bool "386"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32 && !UML
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
---help---
|
|
|
|
This is the processor type of your CPU. This information is used for
|
|
|
|
optimizing purposes. In order to compile a kernel that can run on
|
|
|
|
all x86 CPU types (albeit not optimally fast), you can specify
|
|
|
|
"386" here.
|
|
|
|
|
|
|
|
The kernel will not necessarily run on earlier architectures than
|
|
|
|
the one you have chosen, e.g. a Pentium optimized kernel will run on
|
|
|
|
a PPro, but not necessarily on a i486.
|
|
|
|
|
|
|
|
Here are the settings recommended for greatest speed:
|
|
|
|
- "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
|
|
|
|
486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels
|
|
|
|
will run on a 386 class machine.
|
|
|
|
- "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
|
|
|
|
SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
|
|
|
|
- "586" for generic Pentium CPUs lacking the TSC
|
|
|
|
(time stamp counter) register.
|
|
|
|
- "Pentium-Classic" for the Intel Pentium.
|
|
|
|
- "Pentium-MMX" for the Intel Pentium MMX.
|
|
|
|
- "Pentium-Pro" for the Intel Pentium Pro.
|
|
|
|
- "Pentium-II" for the Intel Pentium II or pre-Coppermine Celeron.
|
|
|
|
- "Pentium-III" for the Intel Pentium III or Coppermine Celeron.
|
|
|
|
- "Pentium-4" for the Intel Pentium 4 or P4-based Celeron.
|
|
|
|
- "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
|
|
|
|
- "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
|
|
|
|
- "Crusoe" for the Transmeta Crusoe series.
|
|
|
|
- "Efficeon" for the Transmeta Efficeon series.
|
|
|
|
- "Winchip-C6" for original IDT Winchip.
|
|
|
|
- "Winchip-2" for IDT Winchip 2.
|
|
|
|
- "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
|
|
|
|
- "GeodeGX1" for Geode GX1 (Cyrix MediaGX).
|
2006-01-06 01:12:14 -07:00
|
|
|
- "Geode GX/LX" For AMD Geode GX and LX processors.
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
- "CyrixIII/VIA C3" for VIA Cyrix III or VIA C3.
|
2006-06-26 09:47:15 -07:00
|
|
|
- "VIA C3-2" for VIA C3-2 "Nehemiah" (model 9 and above).
|
2007-05-02 10:27:05 -07:00
|
|
|
- "VIA C7" for VIA C7.
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
If you don't know what to do, choose "386".
|
|
|
|
|
|
|
|
config M486
|
|
|
|
bool "486"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a 486 series processor, either Intel or one of the
|
|
|
|
compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,
|
|
|
|
DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
|
|
|
|
U5S.
|
|
|
|
|
|
|
|
config M586
|
|
|
|
bool "586/K5/5x86/6x86/6x86MX"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for an 586 or 686 series processor such as the AMD K5,
|
|
|
|
the Cyrix 5x86, 6x86 and 6x86MX. This choice does not
|
|
|
|
assume the RDTSC (Read Time Stamp Counter) instruction.
|
|
|
|
|
|
|
|
config M586TSC
|
|
|
|
bool "Pentium-Classic"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a Pentium Classic processor with the RDTSC (Read
|
|
|
|
Time Stamp Counter) instruction for benchmarking.
|
|
|
|
|
|
|
|
config M586MMX
|
|
|
|
bool "Pentium-MMX"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a Pentium with the MMX graphics/multimedia
|
|
|
|
extended instructions.
|
|
|
|
|
|
|
|
config M686
|
|
|
|
bool "Pentium-Pro"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for Intel Pentium Pro chips. This enables the use of
|
|
|
|
Pentium Pro extended instructions, and disables the init-time guard
|
|
|
|
against the f00f bug found in earlier Pentiums.
|
|
|
|
|
|
|
|
config MPENTIUMII
|
|
|
|
bool "Pentium-II/Celeron(pre-Coppermine)"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for Intel chips based on the Pentium-II and
|
|
|
|
pre-Coppermine Celeron core. This option enables an unaligned
|
|
|
|
copy optimization, compiles the kernel with optimization flags
|
|
|
|
tailored for the chip, and applies any applicable Pentium Pro
|
|
|
|
optimizations.
|
|
|
|
|
|
|
|
config MPENTIUMIII
|
|
|
|
bool "Pentium-III/Celeron(Coppermine)/Pentium-III Xeon"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for Intel chips based on the Pentium-III and
|
|
|
|
Celeron-Coppermine core. This option enables use of some
|
|
|
|
extended prefetch instructions in addition to the Pentium II
|
|
|
|
extensions.
|
|
|
|
|
|
|
|
config MPENTIUMM
|
|
|
|
bool "Pentium M"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for Intel Pentium M (not Pentium-4 M)
|
|
|
|
notebook chips.
|
|
|
|
|
|
|
|
config MPENTIUM4
|
2006-12-06 18:14:09 -07:00
|
|
|
bool "Pentium-4/Celeron(P4-based)/Pentium-4 M/older Xeon"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for Intel Pentium 4 chips. This includes the
|
2007-10-17 09:04:36 -07:00
|
|
|
Pentium 4, Pentium D, P4-based Celeron and Xeon, and
|
|
|
|
Pentium-4 M (not Pentium M) chips. This option enables compile
|
|
|
|
flags optimized for the chip, uses the correct cache line size, and
|
|
|
|
applies any applicable optimizations.
|
|
|
|
|
|
|
|
CPUIDs: F[0-6][1-A] (in /proc/cpuinfo show = cpu family : 15 )
|
|
|
|
|
|
|
|
Select this for:
|
|
|
|
Pentiums (Pentium 4, Pentium D, Celeron, Celeron D) corename:
|
|
|
|
-Willamette
|
|
|
|
-Northwood
|
|
|
|
-Mobile Pentium 4
|
|
|
|
-Mobile Pentium 4 M
|
|
|
|
-Extreme Edition (Gallatin)
|
|
|
|
-Prescott
|
|
|
|
-Prescott 2M
|
|
|
|
-Cedar Mill
|
|
|
|
-Presler
|
|
|
|
-Smithfiled
|
|
|
|
Xeons (Intel Xeon, Xeon MP, Xeon LV, Xeon MV) corename:
|
|
|
|
-Foster
|
|
|
|
-Prestonia
|
|
|
|
-Gallatin
|
|
|
|
-Nocona
|
|
|
|
-Irwindale
|
|
|
|
-Cranford
|
|
|
|
-Potomac
|
|
|
|
-Paxville
|
|
|
|
-Dempsey
|
|
|
|
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config MK6
|
|
|
|
bool "K6/K6-II/K6-III"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for an AMD K6-family processor. Enables use of
|
|
|
|
some extended instructions, and passes appropriate optimization
|
|
|
|
flags to GCC.
|
|
|
|
|
|
|
|
config MK7
|
|
|
|
bool "Athlon/Duron/K7"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for an AMD Athlon K7-family processor. Enables use of
|
|
|
|
some extended instructions, and passes appropriate optimization
|
|
|
|
flags to GCC.
|
|
|
|
|
|
|
|
config MK8
|
|
|
|
bool "Opteron/Athlon64/Hammer/K8"
|
|
|
|
help
|
|
|
|
Select this for an AMD Opteron or Athlon64 Hammer-family processor. Enables
|
|
|
|
use of some extended instructions, and passes appropriate optimization
|
|
|
|
flags to GCC.
|
|
|
|
|
|
|
|
config MCRUSOE
|
|
|
|
bool "Crusoe"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a Transmeta Crusoe processor. Treats the processor
|
|
|
|
like a 586 with TSC, and sets some GCC optimization flags (like a
|
|
|
|
Pentium Pro with no alignment requirements).
|
|
|
|
|
|
|
|
config MEFFICEON
|
|
|
|
bool "Efficeon"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a Transmeta Efficeon processor.
|
|
|
|
|
|
|
|
config MWINCHIPC6
|
|
|
|
bool "Winchip-C6"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for an IDT Winchip C6 chip. Linux and GCC
|
|
|
|
treat this chip as a 586TSC with some extended instructions
|
|
|
|
and alignment requirements.
|
|
|
|
|
|
|
|
config MWINCHIP2
|
|
|
|
bool "Winchip-2"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for an IDT Winchip-2. Linux and GCC
|
|
|
|
treat this chip as a 586TSC with some extended instructions
|
|
|
|
and alignment requirements.
|
|
|
|
|
|
|
|
config MWINCHIP3D
|
|
|
|
bool "Winchip-2A/Winchip-3"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for an IDT Winchip-2A or 3. Linux and GCC
|
|
|
|
treat this chip as a 586TSC with some extended instructions
|
2007-05-08 22:12:20 -07:00
|
|
|
and alignment requirements. Also enable out of order memory
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
stores for this CPU, which can increase performance of some
|
|
|
|
operations.
|
|
|
|
|
|
|
|
config MGEODEGX1
|
|
|
|
bool "GeodeGX1"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a Geode GX1 (Cyrix MediaGX) chip.
|
|
|
|
|
2006-01-06 01:12:14 -07:00
|
|
|
config MGEODE_LX
|
2008-01-30 05:31:03 -07:00
|
|
|
bool "Geode GX/LX"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
2008-01-30 05:31:03 -07:00
|
|
|
help
|
|
|
|
Select this for AMD Geode GX and LX processors.
|
2006-01-06 01:12:14 -07:00
|
|
|
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
config MCYRIXIII
|
|
|
|
bool "CyrixIII/VIA-C3"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a Cyrix III or C3 chip. Presently Linux and GCC
|
|
|
|
treat this chip as a generic 586. Whilst the CPU is 686 class,
|
|
|
|
it lacks the cmov extension which gcc assumes is present when
|
|
|
|
generating 686 code.
|
|
|
|
Note that Nehemiah (Model 9) and above will not boot with this
|
|
|
|
kernel due to them lacking the 3DNow! instructions used in earlier
|
|
|
|
incarnations of the CPU.
|
|
|
|
|
|
|
|
config MVIAC3_2
|
|
|
|
bool "VIA C3-2 (Nehemiah)"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
help
|
|
|
|
Select this for a VIA C3 "Nehemiah". Selecting this enables usage
|
|
|
|
of SSE and tells gcc to treat the CPU as a 686.
|
|
|
|
Note, this kernel will not boot on older (pre model 9) C3s.
|
|
|
|
|
2007-05-02 10:27:05 -07:00
|
|
|
config MVIAC7
|
|
|
|
bool "VIA C7"
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32
|
2007-05-02 10:27:05 -07:00
|
|
|
help
|
|
|
|
Select this for a VIA C7. Selecting this uses the correct cache
|
|
|
|
shift and tells gcc to treat the CPU as a 686.
|
|
|
|
|
2007-11-06 13:35:08 -07:00
|
|
|
config MPSC
|
|
|
|
bool "Intel P4 / older Netburst based Xeon"
|
|
|
|
depends on X86_64
|
|
|
|
help
|
|
|
|
Optimize for Intel Pentium 4, Pentium D and older Nocona/Dempsey
|
|
|
|
Xeon CPUs with Intel 64bit which is compatible with x86-64.
|
|
|
|
Note that the latest Xeons (Xeon 51xx and 53xx) are not based on the
|
2008-01-30 05:31:03 -07:00
|
|
|
Netburst core and shouldn't use this option. You can distinguish them
|
2007-11-06 13:35:08 -07:00
|
|
|
using the cpu family field
|
|
|
|
in /proc/cpuinfo. Family 15 is an older Xeon, Family 6 a newer one.
|
|
|
|
|
|
|
|
config MCORE2
|
|
|
|
bool "Core 2/newer Xeon"
|
|
|
|
help
|
|
|
|
Select this for Intel Core 2 and newer Core 2 Xeons (Xeon 51xx and 53xx)
|
|
|
|
CPUs. You can distinguish newer from older Xeons by the CPU family
|
|
|
|
in /proc/cpuinfo. Newer ones have 6 and older ones 15 (not a typo)
|
|
|
|
|
|
|
|
config GENERIC_CPU
|
|
|
|
bool "Generic-x86-64"
|
|
|
|
depends on X86_64
|
|
|
|
help
|
|
|
|
Generic x86-64 CPU.
|
|
|
|
Run equally well on all x86-64 CPUs.
|
|
|
|
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
config X86_GENERIC
|
2007-11-06 13:35:08 -07:00
|
|
|
bool "Generic x86 support"
|
|
|
|
depends on X86_32
|
|
|
|
help
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
Instead of just including optimizations for the selected
|
|
|
|
x86 variant (e.g. PII, Crusoe or Athlon), include some more
|
|
|
|
generic optimizations as well. This will make the kernel
|
|
|
|
perform better on x86 CPUs other than that selected.
|
|
|
|
|
|
|
|
This is really intended for distributors who need more
|
|
|
|
generic optimizations.
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Define implied options from the CPU selection here
|
2007-11-06 13:35:08 -07:00
|
|
|
config X86_L1_CACHE_BYTES
|
|
|
|
int
|
|
|
|
default "128" if GENERIC_CPU || MPSC
|
|
|
|
default "64" if MK8 || MCORE2
|
|
|
|
depends on X86_64
|
|
|
|
|
|
|
|
config X86_INTERNODE_CACHE_BYTES
|
|
|
|
int
|
|
|
|
default "4096" if X86_VSMP
|
|
|
|
default X86_L1_CACHE_BYTES if !X86_VSMP
|
|
|
|
depends on X86_64
|
|
|
|
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
config X86_CMPXCHG
|
2007-11-06 13:35:08 -07:00
|
|
|
def_bool X86_64 || (X86_32 && !M386)
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_L1_CACHE_SHIFT
|
|
|
|
int
|
2007-11-06 13:35:08 -07:00
|
|
|
default "7" if MPENTIUM4 || X86_GENERIC || GENERIC_CPU || MPSC
|
2006-01-06 01:12:14 -07:00
|
|
|
default "4" if X86_ELAN || M486 || M386 || MGEODEGX1
|
|
|
|
default "5" if MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCRUSOE || MEFFICEON || MCYRIXIII || MK6 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || M586 || MVIAC3_2 || MGEODE_LX
|
2007-05-02 10:27:05 -07:00
|
|
|
default "6" if MK7 || MK8 || MPENTIUMM || MCORE2 || MVIAC7
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
2007-05-02 10:27:20 -07:00
|
|
|
config X86_XADD
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32 && !M386
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_PPRO_FENCE
|
2008-01-30 05:32:31 -07:00
|
|
|
bool "PentiumPro memory ordering errata workaround"
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
depends on M686 || M586MMX || M586TSC || M586 || M486 || M386 || MGEODEGX1
|
2008-01-30 05:32:31 -07:00
|
|
|
help
|
|
|
|
Old PentiumPro multiprocessor systems had errata that could cause memory
|
|
|
|
operations to violate the x86 ordering standard in rare cases. Enabling this
|
|
|
|
option will attempt to work around some (but not all) occurances of
|
|
|
|
this problem, at the cost of much heavier spinlock and memory barrier
|
|
|
|
operations.
|
|
|
|
|
|
|
|
If unsure, say n here. Even distro kernels should think twice before enabling
|
|
|
|
this: there are few systems, and an unlikely bug.
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_F00F_BUG
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
depends on M586MMX || M586TSC || M586 || M486 || M386
|
|
|
|
|
|
|
|
config X86_WP_WORKS_OK
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32 && !M386
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_INVLPG
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32 && !M386
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_BSWAP
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32 && !M386
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_POPAD_OK
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on X86_32 && !M386
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_ALIGNMENT_16
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
depends on MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCYRIXIII || X86_ELAN || MK6 || M586MMX || M586TSC || M586 || M486 || MVIAC3_2 || MGEODEGX1
|
|
|
|
|
|
|
|
config X86_GOOD_APIC
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on MK7 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || MK8 || MEFFICEON || MCORE2 || MVIAC7 || X86_64
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_INTEL_USERCOPY
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2006-12-06 18:14:09 -07:00
|
|
|
depends on MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M586MMX || X86_GENERIC || MK8 || MK7 || MEFFICEON || MCORE2
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_USE_PPRO_CHECKSUM
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2006-12-06 18:14:09 -07:00
|
|
|
depends on MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MK8 || MVIAC3_2 || MEFFICEON || MGEODE_LX || MCORE2
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_USE_3DNOW
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2006-10-11 01:21:35 -07:00
|
|
|
depends on (MCYRIXIII || MK7 || MGEODE_LX) && !UML
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
|
|
|
|
config X86_OOSTORE
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
depends on (MWINCHIP3D || MWINCHIP2 || MWINCHIPC6) && MTRR
|
|
|
|
|
2008-02-14 15:56:45 -07:00
|
|
|
#
|
|
|
|
# P6_NOPs are a relatively minor optimization that require a family >=
|
|
|
|
# 6 processor, except that it is broken on certain VIA chips.
|
|
|
|
# Furthermore, AMD chips prefer a totally different sequence of NOPs
|
|
|
|
# (which work on all CPUs). As a result, disallow these if we're
|
|
|
|
# compiling X86_GENERIC but not X86_64 (these NOPs do work on all
|
|
|
|
# x86-64 capable chips); the list of processors in the right-hand clause
|
|
|
|
# are the cores that benefit from this optimization.
|
|
|
|
#
|
2008-02-14 15:52:05 -07:00
|
|
|
config X86_P6_NOP
|
|
|
|
def_bool y
|
2008-04-03 15:48:29 -07:00
|
|
|
depends on (X86_64 || !X86_GENERIC) && (M686 || MPENTIUMII || MPENTIUMIII || MPENTIUMM || MCORE2 || MPENTIUM4 || MPSC)
|
2008-02-14 15:52:05 -07:00
|
|
|
|
[PATCH] uml: reuse i386 cpu-specific tuning
Make UML share the underlying cpu-specific tuning done on i386.
Actually, for now many config options aren't used a lot - but that can be done
later. Also, UML relies on GCC optimization for things like memcpy and such
more than i386, so specifying the correct -march and -mtune should be enough.
Later, we may want to correct some other stuff.
For instance, since FPU context switching, for us, is done (at least
partially, i.e. between our kernelspace and userspace) by the host, we may
allow usage of FPU operations by GCC. This doesn't hold for kernelspace vs.
kernelspace, but we don't support preemption.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-30 16:00:07 -07:00
|
|
|
config X86_TSC
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-11-06 13:35:08 -07:00
|
|
|
depends on ((MWINCHIP3D || MWINCHIP2 || MCRUSOE || MEFFICEON || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || MK8 || MVIAC3_2 || MVIAC7 || MGEODEGX1 || MGEODE_LX || MCORE2) && !X86_NUMAQ) || X86_64
|
2007-05-02 10:27:20 -07:00
|
|
|
|
|
|
|
# this should be set for all -march=.. options where the compiler
|
|
|
|
# generates cmov.
|
|
|
|
config X86_CMOV
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2007-05-02 10:27:20 -07:00
|
|
|
depends on (MK7 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7)
|
|
|
|
|
2007-07-11 12:18:30 -07:00
|
|
|
config X86_MINIMUM_CPU_FAMILY
|
2007-05-02 10:27:20 -07:00
|
|
|
int
|
2007-11-06 13:35:08 -07:00
|
|
|
default "64" if X86_64
|
2008-02-14 15:52:05 -07:00
|
|
|
default "6" if X86_32 && X86_P6_NOP
|
2007-11-06 13:35:08 -07:00
|
|
|
default "4" if X86_32 && (X86_XADD || X86_CMPXCHG || X86_BSWAP || X86_WP_WORKS_OK)
|
2007-07-11 12:18:30 -07:00
|
|
|
default "3"
|
2007-05-02 10:27:20 -07:00
|
|
|
|
2008-01-30 05:30:54 -07:00
|
|
|
config X86_DEBUGCTLMSR
|
2008-01-30 05:31:03 -07:00
|
|
|
def_bool y
|
2008-01-30 05:30:54 -07:00
|
|
|
depends on !(M586MMX || M586TSC || M586 || M486 || M386)
|