License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 14:07:57 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
[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 23:00:07 +00:00
|
|
|
# Put here option for CPU selection and depending optimization
|
|
|
|
|
choice
|
|
|
|
|
prompt "Processor family"
|
2007-11-06 20:35:08 +00:00
|
|
|
default M686 if X86_32
|
|
|
|
|
default GENERIC_CPU if X86_64
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2012-11-28 19:50:23 +00:00
|
|
|
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 supported x86 CPU types (albeit not
|
|
|
|
|
optimally fast), you can specify "486" here.
|
|
|
|
|
|
|
|
|
|
Note that the 386 is no longer supported, this includes
|
|
|
|
|
AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI 486DLC/DLC2,
|
2012-11-29 21:28:39 +00:00
|
|
|
UMC 486SX-S and the NexGen Nx586.
|
[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 23:00:07 +00:00
|
|
|
|
|
|
|
|
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:
|
|
|
|
|
- "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
|
2015-10-19 08:41:17 +00:00
|
|
|
SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
|
[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 23:00:07 +00:00
|
|
|
- "586" for generic Pentium CPUs lacking the TSC
|
2015-10-19 08:41:17 +00:00
|
|
|
(time stamp counter) register.
|
[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 23:00:07 +00:00
|
|
|
- "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).
|
2015-10-19 08:41:17 +00:00
|
|
|
- "Opteron/Athlon64/Hammer/K8" for all K8 and newer AMD 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 23:00:07 +00:00
|
|
|
- "Crusoe" for the Transmeta Crusoe series.
|
|
|
|
|
- "Efficeon" for the Transmeta Efficeon series.
|
|
|
|
|
- "Winchip-C6" for original IDT Winchip.
|
2008-09-28 19:28:15 +00:00
|
|
|
- "Winchip-2" for IDT Winchips with 3dNow! capabilities.
|
2015-10-19 08:41:17 +00:00
|
|
|
- "AMD Elan" for the 32-bit AMD Elan embedded CPU.
|
[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 23:00:07 +00:00
|
|
|
- "GeodeGX1" for Geode GX1 (Cyrix MediaGX).
|
2006-01-06 08:12:14 +00: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 23:00:07 +00:00
|
|
|
- "CyrixIII/VIA C3" for VIA Cyrix III or VIA C3.
|
2006-06-26 16:47:15 +00:00
|
|
|
- "VIA C3-2" for VIA C3-2 "Nehemiah" (model 9 and above).
|
2007-05-02 17:27:05 +00:00
|
|
|
- "VIA C7" for VIA C7.
|
2015-10-19 08:41:17 +00:00
|
|
|
- "Intel P4" for the Pentium 4/Netburst microarchitecture.
|
|
|
|
|
- "Core 2/newer Xeon" for all core2 and newer Intel CPUs.
|
|
|
|
|
- "Intel Atom" for the Atom-microarchitecture CPUs.
|
|
|
|
|
- "Generic-x86-64" for a kernel which runs on any x86-64 CPU.
|
|
|
|
|
|
|
|
|
|
See each option's help text for additional details. If you don't know
|
|
|
|
|
what to do, choose "486".
|
[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 23:00:07 +00:00
|
|
|
|
2019-10-01 14:23:35 +00:00
|
|
|
config M486SX
|
|
|
|
|
bool "486SX"
|
|
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-10-01 14:23:35 +00:00
|
|
|
Select this for an 486-class CPU without an FPU such as
|
|
|
|
|
AMD/Cyrix/IBM/Intel SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5S.
|
|
|
|
|
|
2015-10-19 08:41:17 +00:00
|
|
|
config M486
|
2019-10-01 14:23:35 +00:00
|
|
|
bool "486DX"
|
2015-10-19 08:41:17 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2015-10-19 08:41:17 +00:00
|
|
|
Select this for an 486-class CPU such as AMD/Cyrix/IBM/Intel
|
2019-10-01 14:23:35 +00:00
|
|
|
486DX/DX2/DX4 and UMC U5D.
|
[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 23:00:07 +00:00
|
|
|
|
|
|
|
|
config M586
|
|
|
|
|
bool "586/K5/5x86/6x86/6x86MX"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
Select this for a Pentium with the MMX graphics/multimedia
|
|
|
|
|
extended instructions.
|
|
|
|
|
|
|
|
|
|
config M686
|
|
|
|
|
bool "Pentium-Pro"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
Select this for Intel Pentium M (not Pentium-4 M)
|
|
|
|
|
notebook chips.
|
|
|
|
|
|
|
|
|
|
config MPENTIUM4
|
2006-12-07 01:14:09 +00:00
|
|
|
bool "Pentium-4/Celeron(P4-based)/Pentium-4 M/older Xeon"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
Select this for Intel Pentium 4 chips. This includes the
|
2007-10-17 16:04:36 +00: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 23:00:07 +00:00
|
|
|
|
|
|
|
|
config MK6
|
|
|
|
|
bool "K6/K6-II/K6-III"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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"
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2009-02-04 20:44:04 +00:00
|
|
|
Select this for an AMD Opteron or Athlon64 Hammer-family processor.
|
|
|
|
|
Enables use of some extended instructions, and passes appropriate
|
|
|
|
|
optimization flags to GCC.
|
[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 23:00:07 +00:00
|
|
|
|
|
|
|
|
config MCRUSOE
|
|
|
|
|
bool "Crusoe"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
Select this for a Transmeta Efficeon processor.
|
|
|
|
|
|
|
|
|
|
config MWINCHIPC6
|
|
|
|
|
bool "Winchip-C6"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 MWINCHIP3D
|
2008-09-28 19:28:15 +00:00
|
|
|
bool "Winchip-2/Winchip-2A/Winchip-3"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-09-28 19:28:15 +00:00
|
|
|
Select this for an IDT Winchip-2, 2A or 3. Linux and GCC
|
[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 23:00:07 +00:00
|
|
|
treat this chip as a 586TSC with some extended instructions
|
2007-05-09 05:12:20 +00: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 23:00:07 +00:00
|
|
|
stores for this CPU, which can increase performance of some
|
|
|
|
|
operations.
|
|
|
|
|
|
2011-04-08 06:42:29 +00:00
|
|
|
config MELAN
|
|
|
|
|
bool "AMD Elan"
|
|
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2011-04-08 06:42:29 +00:00
|
|
|
Select this for an AMD Elan processor.
|
|
|
|
|
|
|
|
|
|
Do not use this option for K6/Athlon/Opteron 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 23:00:07 +00:00
|
|
|
config MGEODEGX1
|
|
|
|
|
bool "GeodeGX1"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
Select this for a Geode GX1 (Cyrix MediaGX) chip.
|
|
|
|
|
|
2006-01-06 08:12:14 +00:00
|
|
|
config MGEODE_LX
|
2008-01-30 12:31:03 +00:00
|
|
|
bool "Geode GX/LX"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-01-30 12:31:03 +00:00
|
|
|
Select this for AMD Geode GX and LX processors.
|
2006-01-06 08:12:14 +00: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 23:00:07 +00:00
|
|
|
config MCYRIXIII
|
|
|
|
|
bool "CyrixIII/VIA-C3"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
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 17:27:05 +00:00
|
|
|
config MVIAC7
|
|
|
|
|
bool "VIA C7"
|
2007-11-06 20:35:08 +00:00
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-05-02 17:27:05 +00:00
|
|
|
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 20:35:08 +00:00
|
|
|
config MPSC
|
|
|
|
|
bool "Intel P4 / older Netburst based Xeon"
|
|
|
|
|
depends on X86_64
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-11-06 20:35:08 +00:00
|
|
|
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 12:31:03 +00:00
|
|
|
Netburst core and shouldn't use this option. You can distinguish them
|
2007-11-06 20:35:08 +00: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"
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2009-02-04 20:44:04 +00:00
|
|
|
|
|
|
|
|
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)
|
2007-11-06 20:35:08 +00:00
|
|
|
|
2009-08-21 21:06:23 +00:00
|
|
|
config MATOM
|
|
|
|
|
bool "Intel Atom"
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2009-08-21 21:06:23 +00:00
|
|
|
|
|
|
|
|
Select this for the Intel Atom platform. Intel Atom CPUs have an
|
|
|
|
|
in-order pipelining architecture and thus can benefit from
|
|
|
|
|
accordingly optimized code. Use a recent GCC with specific Atom
|
|
|
|
|
support in order to fully benefit from selecting this option.
|
|
|
|
|
|
2007-11-06 20:35:08 +00:00
|
|
|
config GENERIC_CPU
|
|
|
|
|
bool "Generic-x86-64"
|
|
|
|
|
depends on X86_64
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-11-06 20:35:08 +00:00
|
|
|
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 23:00:07 +00:00
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config X86_GENERIC
|
2007-11-06 20:35:08 +00:00
|
|
|
bool "Generic x86 support"
|
|
|
|
|
depends on X86_32
|
2020-06-13 16:50:22 +00:00
|
|
|
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 23:00:07 +00: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.
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Define implied options from the CPU selection here
|
2009-11-13 11:54:40 +00:00
|
|
|
config X86_INTERNODE_CACHE_SHIFT
|
2007-11-06 20:35:08 +00:00
|
|
|
int
|
2009-11-13 11:54:40 +00:00
|
|
|
default "12" if X86_VSMP
|
|
|
|
|
default X86_L1_CACHE_SHIFT
|
2007-11-06 20:35:08 +00: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 23:00:07 +00:00
|
|
|
config X86_L1_CACHE_SHIFT
|
|
|
|
|
int
|
2009-01-12 22:37:16 +00:00
|
|
|
default "7" if MPENTIUM4 || MPSC
|
2009-11-13 11:54:40 +00:00
|
|
|
default "6" if MK7 || MK8 || MPENTIUMM || MCORE2 || MATOM || MVIAC7 || X86_GENERIC || GENERIC_CPU
|
2019-10-01 14:23:35 +00:00
|
|
|
default "4" if MELAN || M486SX || M486 || MGEODEGX1
|
2008-09-28 19:28:15 +00:00
|
|
|
default "5" if MWINCHIP3D || MWINCHIPC6 || MCRUSOE || MEFFICEON || MCYRIXIII || MK6 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || M586 || MVIAC3_2 || MGEODE_LX
|
[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 23:00:07 +00:00
|
|
|
|
|
|
|
|
config X86_F00F_BUG
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2019-10-01 14:23:35 +00:00
|
|
|
depends on M586MMX || M586TSC || M586 || M486SX || M486
|
[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 23:00:07 +00:00
|
|
|
|
2010-03-21 13:00:43 +00:00
|
|
|
config X86_INVD_BUG
|
|
|
|
|
def_bool y
|
2019-10-01 14:23:35 +00:00
|
|
|
depends on M486SX || M486
|
2010-03-21 13:00:43 +00: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 23:00:07 +00:00
|
|
|
config X86_ALIGNMENT_16
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2019-10-01 14:23:35 +00:00
|
|
|
depends on MWINCHIP3D || MWINCHIPC6 || MCYRIXIII || MELAN || MK6 || M586MMX || M586TSC || M586 || M486SX || M486 || MVIAC3_2 || MGEODEGX1
|
[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 23:00:07 +00:00
|
|
|
|
|
|
|
|
config X86_INTEL_USERCOPY
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2006-12-07 01:14:09 +00: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 23:00:07 +00:00
|
|
|
|
|
|
|
|
config X86_USE_PPRO_CHECKSUM
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2011-03-16 15:32:47 +00:00
|
|
|
depends on MWINCHIP3D || MWINCHIPC6 || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MK8 || MVIAC3_2 || MVIAC7 || MEFFICEON || MGEODE_LX || MCORE2 || MATOM
|
[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 23:00:07 +00:00
|
|
|
|
|
|
|
|
config X86_USE_3DNOW
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2006-10-11 08:21:35 +00: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 23:00:07 +00:00
|
|
|
|
2008-02-14 22:56:45 +00: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
|
2008-09-05 16:30:14 +00:00
|
|
|
# (which work on all CPUs). In addition, it looks like Virtual PC
|
|
|
|
|
# does not understand them.
|
|
|
|
|
#
|
|
|
|
|
# As a result, disallow these if we're not compiling for 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 22:56:45 +00:00
|
|
|
#
|
2008-02-14 22:52:05 +00:00
|
|
|
config X86_P6_NOP
|
|
|
|
|
def_bool y
|
2008-09-05 16:30:14 +00:00
|
|
|
depends on X86_64
|
|
|
|
|
depends on (MCORE2 || MPENTIUM4 || MPSC)
|
2008-02-14 22:52:05 +00: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 23:00:07 +00:00
|
|
|
config X86_TSC
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2014-02-25 20:14:06 +00:00
|
|
|
depends on (MWINCHIP3D || MCRUSOE || MEFFICEON || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || MK8 || MVIAC3_2 || MVIAC7 || MGEODEGX1 || MGEODE_LX || MCORE2 || MATOM) || X86_64
|
2007-05-02 17:27:20 +00:00
|
|
|
|
2008-04-22 15:27:29 +00:00
|
|
|
config X86_CMPXCHG64
|
|
|
|
|
def_bool y
|
2018-02-15 16:54:54 +00:00
|
|
|
depends on X86_PAE || X86_64 || MCORE2 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || M586TSC || M586MMX || MATOM || MGEODE_LX || MGEODEGX1 || MK6 || MK7 || MK8
|
2008-04-22 15:27:29 +00:00
|
|
|
|
2007-05-02 17:27:20 +00:00
|
|
|
# this should be set for all -march=.. options where the compiler
|
|
|
|
|
# generates cmov.
|
|
|
|
|
config X86_CMOV
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2009-10-01 15:11:10 +00:00
|
|
|
depends on (MK8 || MK7 || MCORE2 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7 || MCRUSOE || MEFFICEON || X86_64 || MATOM || MGEODE_LX)
|
2007-05-02 17:27:20 +00:00
|
|
|
|
2007-07-11 19:18:30 +00:00
|
|
|
config X86_MINIMUM_CPU_FAMILY
|
2007-05-02 17:27:20 +00:00
|
|
|
int
|
2007-11-06 20:35:08 +00:00
|
|
|
default "64" if X86_64
|
2018-02-15 16:54:56 +00:00
|
|
|
default "6" if X86_32 && (MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7 || MEFFICEON || MATOM || MCRUSOE || MCORE2 || MK7 || MK8)
|
2009-10-01 00:57:27 +00:00
|
|
|
default "5" if X86_32 && X86_CMPXCHG64
|
2012-11-28 19:50:23 +00:00
|
|
|
default "4"
|
2007-05-02 17:27:20 +00:00
|
|
|
|
2008-01-30 12:30:54 +00:00
|
|
|
config X86_DEBUGCTLMSR
|
2008-01-30 12:31:03 +00:00
|
|
|
def_bool y
|
2019-10-01 14:23:35 +00:00
|
|
|
depends on !(MK6 || MWINCHIPC6 || MWINCHIP3D || MCYRIXIII || M586MMX || M586TSC || M586 || M486SX || M486) && !UML
|
2008-08-05 09:45:19 +00:00
|
|
|
|
2019-12-21 04:44:58 +00:00
|
|
|
config IA32_FEAT_CTL
|
|
|
|
|
def_bool y
|
2019-12-21 04:45:01 +00:00
|
|
|
depends on CPU_SUP_INTEL || CPU_SUP_CENTAUR || CPU_SUP_ZHAOXIN
|
2019-12-21 04:44:58 +00:00
|
|
|
|
2019-12-21 04:45:04 +00:00
|
|
|
config X86_VMX_FEATURE_NAMES
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on IA32_FEAT_CTL && X86_FEATURE_NAMES
|
|
|
|
|
|
2008-08-05 09:45:19 +00:00
|
|
|
menuconfig PROCESSOR_SELECT
|
2011-01-20 22:44:16 +00:00
|
|
|
bool "Supported processor vendors" if EXPERT
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-08-05 09:45:19 +00:00
|
|
|
This lets you choose what x86 vendor support code your kernel
|
|
|
|
|
will include.
|
|
|
|
|
|
2008-09-09 23:40:37 +00:00
|
|
|
config CPU_SUP_INTEL
|
2008-08-05 09:45:19 +00:00
|
|
|
default y
|
|
|
|
|
bool "Support Intel processors" if PROCESSOR_SELECT
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-10-12 13:36:24 +00:00
|
|
|
This enables detection, tunings and quirks for Intel processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on an
|
|
|
|
|
Intel CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on an Intel
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2008-08-05 09:45:19 +00:00
|
|
|
|
|
|
|
|
config CPU_SUP_CYRIX_32
|
|
|
|
|
default y
|
|
|
|
|
bool "Support Cyrix processors" if PROCESSOR_SELECT
|
2019-10-01 14:23:35 +00:00
|
|
|
depends on M486SX || M486 || M586 || M586TSC || M586MMX || (EXPERT && !64BIT)
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-10-12 13:36:24 +00:00
|
|
|
This enables detection, tunings and quirks for Cyrix processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on a
|
|
|
|
|
Cyrix CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on a Cyrix
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2008-08-05 09:45:19 +00:00
|
|
|
|
2008-09-08 00:58:56 +00:00
|
|
|
config CPU_SUP_AMD
|
2008-08-05 09:45:19 +00:00
|
|
|
default y
|
|
|
|
|
bool "Support AMD processors" if PROCESSOR_SELECT
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-10-12 13:36:24 +00:00
|
|
|
This enables detection, tunings and quirks for AMD processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on an
|
|
|
|
|
AMD CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on an AMD
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2008-08-05 09:45:19 +00:00
|
|
|
|
2018-09-23 09:33:12 +00:00
|
|
|
config CPU_SUP_HYGON
|
|
|
|
|
default y
|
|
|
|
|
bool "Support Hygon processors" if PROCESSOR_SELECT
|
|
|
|
|
select CPU_SUP_AMD
|
|
|
|
|
help
|
|
|
|
|
This enables detection, tunings and quirks for Hygon processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on an
|
|
|
|
|
Hygon CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on an Hygon
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-03-14 11:24:02 +00:00
|
|
|
config CPU_SUP_CENTAUR
|
2008-08-05 09:45:19 +00:00
|
|
|
default y
|
|
|
|
|
bool "Support Centaur processors" if PROCESSOR_SELECT
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-10-12 13:36:24 +00:00
|
|
|
This enables detection, tunings and quirks for Centaur processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on a
|
|
|
|
|
Centaur CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on a Centaur
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2008-08-05 09:45:19 +00:00
|
|
|
|
|
|
|
|
config CPU_SUP_TRANSMETA_32
|
|
|
|
|
default y
|
|
|
|
|
bool "Support Transmeta processors" if PROCESSOR_SELECT
|
|
|
|
|
depends on !64BIT
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-10-12 13:36:24 +00:00
|
|
|
This enables detection, tunings and quirks for Transmeta processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on a
|
|
|
|
|
Transmeta CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on a Transmeta
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2008-08-05 09:45:19 +00:00
|
|
|
|
|
|
|
|
config CPU_SUP_UMC_32
|
|
|
|
|
default y
|
|
|
|
|
bool "Support UMC processors" if PROCESSOR_SELECT
|
2019-10-01 14:23:35 +00:00
|
|
|
depends on M486SX || M486 || (EXPERT && !64BIT)
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-10-12 13:36:24 +00:00
|
|
|
This enables detection, tunings and quirks for UMC processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on a
|
|
|
|
|
UMC CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on a UMC
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2019-06-18 08:37:05 +00:00
|
|
|
|
|
|
|
|
config CPU_SUP_ZHAOXIN
|
|
|
|
|
default y
|
|
|
|
|
bool "Support Zhaoxin processors" if PROCESSOR_SELECT
|
|
|
|
|
help
|
|
|
|
|
This enables detection, tunings and quirks for Zhaoxin processors
|
|
|
|
|
|
|
|
|
|
You need this enabled if you want your kernel to run on a
|
|
|
|
|
Zhaoxin CPU. Disabling this option on other types of CPUs
|
|
|
|
|
makes the kernel a tiny bit smaller. Disabling it on a Zhaoxin
|
|
|
|
|
CPU might render the kernel unbootable.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
