x86: 32-bit cleanups
Subsystems (11)
v2 cover x86: 32-bit cleanups
From: Arnd Bergmann <[email protected]>
[sorry for sending a duplicate series, I just noticed I had
dropped lkml from cc when I sent this a few minutes ago]
While looking at 32-bit arm cleanups, I came across some related topics on x86 and ended up making a series for those as well.
Primarily this is about running 32-bit kernels on 64-bit hardware, which usually works but should probably be discouraged more clearly by only providing support for features that are used on real 32-bit hardware:
I found only a few 2003-era high-end servers (HP DL740 and DL760 G2) that were the only possible remaining uses of HIGHMEM64G and BIGSMP after the removal of 32-bit NUMA machines in 2014. Similary, there is only one generation of hardware with support for VT-x. All these features can be removed without hurting users.
In the CPU selection, building a 32-bit kernel optimized for AMD K8 or Intel Core2 is anachronistic, so instead only 32-bit CPU types need to be offered as optimization targets. The "generic" target on 64-bit turned out to be slightly broken, so I included a fix for that as well.
Changes since v1:
- Don't include patch to drop 32-bit KVM support for now
- Drop patch for 64-bit Silverlake support
- Drop 64-bit ISA level selection, only fix default
- Rework MID patch based on comments
- Add a patch to reorganize platform selection
- Add a patch to add -march=native compilation
Arnd Bergmann (11):
x86/Kconfig: Geode CPU has cmpxchg8b
x86: drop 32-bit "bigsmp" machine support
x86: rework CONFIG_GENERIC_CPU compiler flags
x86: drop configuration options for early 64-bit CPUs
x86: add CONFIG_X86_64_NATIVE option
x86: remove HIGHMEM64G support
x86: drop SWIOTLB and PHYS_ADDR_T_64BIT for PAE
x86: drop support for CONFIG_HIGHPTE
x86: document X86_INTEL_MID as 64-bit-only
x86: remove old STA2x11 support
x86: Move platforms to Kconfig.platforms
Documentation/admin-guide/kdump/kdump.rst | 4 - .../admin-guide/kernel-parameters.txt | 11 - Documentation/arch/x86/usb-legacy-support.rst | 11 +- arch/x86/Kconfig | 460 +----------------- arch/x86/Kconfig.cpu | 111 ++--- arch/x86/Kconfig.platforms | 361 ++++++++++++++ arch/x86/Makefile | 21 +- arch/x86/Makefile_32.cpu | 5 +- arch/x86/configs/xen.config | 2 - arch/x86/include/asm/page_32_types.h | 4 +- arch/x86/include/asm/pgalloc.h | 5 - arch/x86/include/asm/sta2x11.h | 13 - arch/x86/include/asm/vermagic.h | 4 - arch/x86/kernel/apic/Makefile | 3 - arch/x86/kernel/apic/apic.c | 3 - arch/x86/kernel/apic/bigsmp_32.c | 105 ---- arch/x86/kernel/apic/local.h | 13 - arch/x86/kernel/apic/probe_32.c | 29 -- arch/x86/mm/init_32.c | 9 +- arch/x86/mm/pgtable.c | 32 +- arch/x86/pci/Makefile | 2 - arch/x86/pci/sta2x11-fixup.c | 233 --------- drivers/misc/mei/Kconfig | 2 +- include/linux/mm.h | 2 +- 24 files changed, 422 insertions(+), 1023 deletions(-) create mode 100644 arch/x86/Kconfig.platforms delete mode 100644 arch/x86/include/asm/sta2x11.h delete mode 100644 arch/x86/kernel/apic/bigsmp_32.c delete mode 100644 arch/x86/pci/sta2x11-fixup.c
Signature · 11 lines
2.39.5 To: [email protected] Cc: Thomas Gleixner <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: Borislav Petkov <[email protected]> Cc: Dave Hansen <[email protected]> Cc: "H. Peter Anvin" <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Andy Shevchenko <[email protected]> Cc: Matthew Wilcox <[email protected]>
PATCH v2 1/11 x86/Kconfig: Geode CPU has cmpxchg8b
From: Arnd Bergmann <[email protected]>
An older cleanup of mine inadvertently removed geode-gx1 and geode-lx from the list of CPUs that are known to support a working cmpxchg8b.
--- arch/x86/Kconfig.cpu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/Kconfig.cpu +1 -1
@@ -368,7 +368,7 @@ config X86_HAVE_PAE config X86_CMPXCHG64 def_bool y - depends on X86_HAVE_PAE || M586TSC || M586MMX || MK6 || MK7 + depends on X86_HAVE_PAE || M586TSC || M586MMX || MK6 || MK7 || MGEODEGX1 || MGEODE_LX # this should be set for all -march=.. options where the compiler # generates cmov.
Signature · 1 line
2.39.5
Re: [PATCH v2 01/11] x86/Kconfig: Geode CPU has cmpxchg8b
Quoted 27 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
An older cleanup of mine inadvertently removed geode-gx1 and geode-lx from the list of CPUs that are known to support a working cmpxchg8b.
Fixes 88a2b4edda3d ("x86/Kconfig: Rework CONFIG_X86_PAE dependency")Signed-off-by Arnd Bergmann <[email protected]>--- arch/x86/Kconfig.cpu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/Kconfig.cpu +1
-2@@ -368,7 +368,7 @@ config X86_HAVE_PAE config X86_CMPXCHG64 def_bool y - depends on X86_HAVE_PAE || M586TSC || M586MMX || MK6 || MK7 + depends on X86_HAVE_PAE || M586TSC || M586MMX || MK6 || MK7 || MGEODEGX1 || MGEODE_LX # this should be set for all -march=.. options where the compiler # generates cmov. --
Quoted 3 lines
2.39.5
An idea for a future cleanup would be to change lists like this to select statements. That would make it easier to see what each CPU option enables.
Brian Gerst
PATCH v2 2/11 x86: drop 32-bit "bigsmp" machine support
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The x86-32 kernel used to support multiple platforms with more than eight logical CPUs, from the 1999-2003 timeframe: Sequent NUMA-Q, IBM Summit, Unisys ES7000 and HP F8. Support for all except the latter was dropped back in 2014, leaving only the F8 based DL740 and DL760 G2 machines in this catery, with up to eight single-core Socket-603 Xeon-MP processors with hyperthreading.
Like the already removed machines, the HP F8 servers at the cost upwards of $100k in typical configurations, but were quickly obsoleted by their 64-bit Socket-604 cousins and the AMD Opteron.
Earlier servers with up to 8 Pentium Pro or Xeon processors remain fully supported as they had no hyperthreading. Similarly, the more common 4-socket Xeon-MP machines with hyperthreading using Intel or ServerWorks chipsets continue to work without this, and all the multi-core Xeon processors also run 64-bit kernels.
While the "bigsmp" support can also be used to run on later 64-bit machines (including VM guests), it seems best to discourage that and get any remaining users to update their kernels to 64-bit builds on these. As a side-effect of this, there is also no more need to support NUMA configurations on 32-bit x86, as all true 32-bit NUMA platforms are already gone.
--- .../admin-guide/kernel-parameters.txt | 4 - arch/x86/Kconfig | 20 +--- arch/x86/kernel/apic/Makefile | 3 - arch/x86/kernel/apic/apic.c | 3 - arch/x86/kernel/apic/bigsmp_32.c | 105 ------------------ arch/x86/kernel/apic/local.h | 13 --- arch/x86/kernel/apic/probe_32.c | 29 ----- 7 files changed, 4 insertions(+), 173 deletions(-) delete mode 100644 arch/x86/kernel/apic/bigsmp_32.c
Documentation/admin-guide/kernel-parameters.txt +0 -4
@@ -410,10 +410,6 @@ Format: { quiet (default) | verbose | debug } Change the amount of debugging information output when initialising the APIC and IO-APIC components. - For X86-32, this can also be used to specify an APIC - driver name. - Format: apic=driver_name - Examples: apic=bigsmp apic_extnmi= [APIC,X86,EARLY] External NMI delivery setting Format: { bsp (default) | all | none }
arch/x86/Kconfig +4 -16
@@ -526,12 +526,6 @@ config X86_FRED ring transitions and exception/interrupt handling if the system supports it. -config X86_BIGSMP - bool "Support for big SMP systems with more than 8 CPUs" - depends on SMP && X86_32 - help - This option is needed for the systems that have more than 8 CPUs. - config X86_EXTENDED_PLATFORM bool "Support for extended (non-PC) x86 platforms" default y
@@ -730,8 +724,8 @@ config X86_32_NON_STANDARD depends on X86_32 && SMP depends on X86_EXTENDED_PLATFORM help - This option compiles in the bigsmp and STA2X11 default - subarchitectures. It is intended for a generic binary + This option compiles in the STA2X11 default + subarchitecture. It is intended for a generic binary kernel. If you select them all, kernel will probe it one by one and will fallback to default.
@@ -1008,8 +1002,7 @@ config NR_CPUS_RANGE_BEGIN config NR_CPUS_RANGE_END int depends on X86_32 - default 64 if SMP && X86_BIGSMP - default 8 if SMP && !X86_BIGSMP + default 8 if SMP default 1 if !SMP config NR_CPUS_RANGE_END
@@ -1022,7 +1015,6 @@ config NR_CPUS_RANGE_END config NR_CPUS_DEFAULT int depends on X86_32 - default 32 if X86_BIGSMP default 8 if SMP default 1 if !SMP
@@ -1568,8 +1560,7 @@ config AMD_MEM_ENCRYPT config NUMA bool "NUMA Memory Allocation and Scheduler Support" depends on SMP - depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP) - default y if X86_BIGSMP + depends on X86_64 select USE_PERCPU_NUMA_NODE_ID select OF_NUMA if OF help
@@ -1582,9 +1573,6 @@ config NUMA For 64-bit this is recommended if the system is Intel Core i7 (or later), AMD Opteron, or EM64T NUMA. - For 32-bit this is only needed if you boot a 32-bit - kernel on a 64-bit NUMA platform. - Otherwise, you should say N. config AMD_NUMA
arch/x86/kernel/apic/Makefile +0 -3
@@ -23,8 +23,5 @@ obj-$(CONFIG_X86_X2APIC) += x2apic_cluster.o obj-y += apic_flat_64.o endif -# APIC probe will depend on the listing order here -obj-$(CONFIG_X86_BIGSMP) += bigsmp_32.o - # For 32bit, probe_32 need to be listed last obj-$(CONFIG_X86_LOCAL_APIC) += probe_$(BITS).o
arch/x86/kernel/apic/apic.c +0 -3
@@ -1371,8 +1371,6 @@ void __init apic_intr_mode_init(void)x86_64_probe_apic (); -x86_32_install_bigsmp (); -if (x86_platform.apic_post_init) x86_platform.apic_post_init ();
@@ -1674,7 +1672,6 @@ static __init void apic_read_boot_cpu_id(bool x2apic) boot_cpu_apic_version =GET_APIC_VERSION (apic_read (APIC_LVR )); }topology_register_boot_apic (boot_cpu_physical_apicid); -x86_32_probe_bigsmp_early (); }#ifdef CONFIG_X86_X2APIC
arch/x86/kernel/apic/bigsmp_32.c deleted +0 -105
105 lines not on this page · raw message
arch/x86/kernel/apic/local.h +0 -13
@@ -65,17 +65,4 @@ void default_send_IPI_self(int vector);void default_send_IPI_mask_sequence_logical (const struct cpumask *mask,int vector);void default_send_IPI_mask_allbutself_logical (const struct cpumask *mask,int vector);void default_send_IPI_mask_logical (const struct cpumask *mask,int vector); -void x86_32_probe_bigsmp_early (void ); -void x86_32_install_bigsmp (void ); -#else -static inline void x86_32_probe_bigsmp_early (void ) { } -static inline void x86_32_install_bigsmp (void ) { } -#endif - -#ifdef CONFIG_X86_BIGSMP -bool apic_bigsmp_possible (bool cmdline_selected); -void apic_bigsmp_force (void ); -#else -static inline bool apic_bigsmp_possible (bool cmdline_selected) {return false; }; -static inline void apic_bigsmp_force (void ) { }#endif
arch/x86/kernel/apic/probe_32.c +0 -29
@@ -93,35 +93,6 @@ static int __init parse_apic(char *arg) }early_param ("apic" , parse_apic); -void __init x86_32_probe_bigsmp_early (void ) -{ -if (nr_cpu_ids <=8 ||xen_pv_domain ()) -return ; - -if (IS_ENABLED (CONFIG_X86_BIGSMP )) { -switch (boot_cpu_data.x86_vendor) { -case X86_VENDOR_INTEL : -if (!APIC_XAPIC (boot_cpu_apic_version)) -break ; -/* P4 and above */ - fallthrough; -case X86_VENDOR_HYGON : -case X86_VENDOR_AMD : -if (apic_bigsmp_possible (cmdline_apic)) -return ; -break ; - } - } -pr_info ("Limiting to 8 possible CPUs\n" ); -set_nr_cpu_ids (8 ); -} - -void __init x86_32_install_bigsmp (void ) -{ -if (nr_cpu_ids >8 && !xen_pv_domain ()) -apic_bigsmp_force (); -} -void __init x86_32_probe_apic (void ) {if (!cmdline_apic) {
Signature · 1 line
2.39.5
PATCH v2 3/11 x86: rework CONFIG_GENERIC_CPU compiler flags
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Building an x86-64 kernel with CONFIG_GENERIC_CPU is documented to run on all CPUs, but the Makefile does not actually pass an -march= argument, instead relying on the default that was used to configure the toolchain.
In many cases, gcc will be configured to -march=x86-64 or -march=k8 for maximum compatibility, but in other cases a distribution default may be either raised to a more recent ISA, or set to -march=native to build for the CPU used for compilation. This still works in the case of building a custom kernel for the local machine.
The point where it breaks down is building a kernel for another machine that is older the the default target. Changing the default to -march=x86-64 would make it work reliable, but possibly produce worse code on distros that intentionally default to a newer ISA.
To allow reliably building a kernel for either the oldest x86-64 CPUs, pass the -march=x86-64 flag to the compiler. This was not possible in early versions of x86-64 gcc, but works on all currently supported versions down to at least gcc-5.
--- arch/x86/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/x86/Makefile +2 -2
@@ -183,14 +183,14 @@ else cflags-$(CONFIG_MPSC) += -march=nocona cflags-$(CONFIG_MCORE2) += -march=core2 cflags-$(CONFIG_MATOM) += -march=atom - cflags-$(CONFIG_GENERIC_CPU) += -mtune=generic + cflags-$(CONFIG_GENERIC_CPU) += -march=x86-64 -mtune=generic KBUILD_CFLAGS += $(cflags-y) rustflags-$(CONFIG_MK8) += -Ctarget-cpu=k8 rustflags-$(CONFIG_MPSC) += -Ctarget-cpu=nocona rustflags-$(CONFIG_MCORE2) += -Ctarget-cpu=core2 rustflags-$(CONFIG_MATOM) += -Ctarget-cpu=atom - rustflags-$(CONFIG_GENERIC_CPU) += -Ztune-cpu=generic + rustflags-$(CONFIG_GENERIC_CPU) += -Ctarget-cpu=x86-64 -Ztune-cpu=generic KBUILD_RUSTFLAGS += $(rustflags-y) KBUILD_CFLAGS += -mno-red-zone
Signature · 1 line
2.39.5
PATCH v2 4/11 x86: drop configuration options for early 64-bit CPUs
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The x86 CPU selection menu is confusing for a number of reasons:
When configuring 32-bit kernels, it shows a small number of early 64-bit microarchitectures (K8, Core 2) but not the regular generic 64-bit target that is the normal default. There is no longer a reason to run 32-bit kernels on production 64-bit systems, so only actual 32-bit CPUs need to be shown here.
When configuring 64-bit kernels, the options also pointless as there is no way to pick any CPU from the past 15 years, leaving GENERIC_CPU as the only sensible choice.
Address both of the above by removing the obsolete options and making all 64-bit kernels run on both Intel and AMD CPUs from any generation. Testing generic 32-bit kernels on 64-bit hardware remains possible, just not building a 32-bit kernel that requires a 64-bit CPU.
--- arch/x86/Kconfig.cpu | 95 +++++---------------------------- arch/x86/Makefile | 16 +----- arch/x86/Makefile_32.cpu | 5 +- arch/x86/include/asm/vermagic.h | 4 -- drivers/misc/mei/Kconfig | 2 +- 5 files changed, 18 insertions(+), 104 deletions(-)
arch/x86/Kconfig.cpu +14 -81
@@ -1,9 +1,9 @@ # SPDX-License-Identifier: GPL-2.0 # Put here option for CPU selection and depending optimization choice - prompt "Processor family" - default M686 if X86_32 - default GENERIC_CPU if X86_64 + prompt "x86-32 Processor family" + depends on X86_32 + default M686 help This is the processor type of your CPU. This information is used for optimizing purposes. In order to compile a kernel
@@ -31,7 +31,6 @@ choice - "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). - - "Opteron/Athlon64/Hammer/K8" for all K8 and newer AMD CPUs. - "Crusoe" for the Transmeta Crusoe series. - "Efficeon" for the Transmeta Efficeon series. - "Winchip-C6" for original IDT Winchip.
@@ -42,13 +41,10 @@ choice - "CyrixIII/VIA C3" for VIA Cyrix III or VIA C3. - "VIA C3-2" for VIA C3-2 "Nehemiah" (model 9 and above). - "VIA C7" for VIA C7. - - "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". + what to do, choose "Pentium-Pro". config M486SX bool "486SX"
@@ -114,11 +110,11 @@ config MPENTIUMIII extensions. config MPENTIUMM - bool "Pentium M" + bool "Pentium M/Pentium Dual Core/Core Solo/Core Duo" depends on X86_32 help Select this for Intel Pentium M (not Pentium-4 M) - notebook chips. + "Merom" Core Solo/Duo notebook chips config MPENTIUM4 bool "Pentium-4/Celeron(P4-based)/Pentium-4 M/older Xeon"
@@ -139,22 +135,10 @@ config MPENTIUM4 -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 - config MK6 bool "K6/K6-II/K6-III"
@@ -172,13 +156,6 @@ config MK7 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" depends on X86_32
@@ -258,42 +235,14 @@ config MVIAC7 Select this for a VIA C7. Selecting this uses the correct cache shift and tells gcc to treat the CPU as a 686. -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 - Netburst core and shouldn't use this option. You can distinguish them - 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 MATOM bool "Intel Atom" help - 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. -config GENERIC_CPU - bool "Generic-x86-64" - depends on X86_64 - help - Generic x86-64 CPU. - Run equally well on all x86-64 CPUs. - endchoice config X86_GENERIC
@@ -317,8 +266,8 @@ config X86_INTERNODE_CACHE_SHIFT config X86_L1_CACHE_SHIFT int - default "7" if MPENTIUM4 || MPSC - default "6" if MK7 || MK8 || MPENTIUMM || MCORE2 || MATOM || MVIAC7 || X86_GENERIC || GENERIC_CPU + default "7" if MPENTIUM4 + default "6" if MK7 || MPENTIUMM || MATOM || MVIAC7 || X86_GENERIC || X86_64 default "4" if MELAN || M486SX || M486 || MGEODEGX1 default "5" if MWINCHIP3D || MWINCHIPC6 || MCRUSOE || MEFFICEON || MCYRIXIII || MK6 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || M586 || MVIAC3_2 || MGEODE_LX
@@ -336,35 +285,19 @@ config X86_ALIGNMENT_16 config X86_INTEL_USERCOPY def_bool y - depends on MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M586MMX || X86_GENERIC || MK8 || MK7 || MEFFICEON || MCORE2 + depends on MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M586MMX || X86_GENERIC || MK7 || MEFFICEON config X86_USE_PPRO_CHECKSUM def_bool y - depends on MWINCHIP3D || MWINCHIPC6 || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MK8 || MVIAC3_2 || MVIAC7 || MEFFICEON || MGEODE_LX || MCORE2 || MATOM - -# -# 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). 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. -# -config X86_P6_NOP - def_bool y - depends on X86_64 - depends on (MCORE2 || MPENTIUM4 || MPSC) + depends on MWINCHIP3D || MWINCHIPC6 || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7 || MEFFICEON || MGEODE_LX || MATOM config X86_TSC def_bool y - 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 + depends on (MWINCHIP3D || MCRUSOE || MEFFICEON || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || MVIAC3_2 || MVIAC7 || MGEODEGX1 || MGEODE_LX || MATOM) || X86_64 config X86_HAVE_PAE def_bool y - depends on MCRUSOE || MEFFICEON || MCYRIXIII || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MK8 || MVIAC7 || MCORE2 || MATOM || X86_64 + depends on MCRUSOE || MEFFICEON || MCYRIXIII || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC7 || MATOM || X86_64 config X86_CMPXCHG64 def_bool y
@@ -374,12 +307,12 @@ config X86_CMPXCHG64 # generates cmov. config X86_CMOV def_bool y - depends on (MK8 || MK7 || MCORE2 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7 || MCRUSOE || MEFFICEON || X86_64 || MATOM || MGEODE_LX) + depends on (MK7 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7 || MCRUSOE || MEFFICEON || MATOM || MGEODE_LX || X86_64) config X86_MINIMUM_CPU_FAMILY int default "64" if X86_64 - default "6" if X86_32 && (MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7 || MEFFICEON || MATOM || MCORE2 || MK7 || MK8) + default "6" if X86_32 && (MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MVIAC3_2 || MVIAC7 || MEFFICEON || MATOM || MK7) default "5" if X86_32 && X86_CMPXCHG64 default "4"
arch/x86/Makefile +2 -14
@@ -178,20 +178,8 @@ else # Use -mskip-rax-setup if supported. KBUILD_CFLAGS += $(call cc-option,-mskip-rax-setup) - # FIXME - should be integrated in Makefile.cpu (Makefile_32.cpu) - cflags-$(CONFIG_MK8) += -march=k8 - cflags-$(CONFIG_MPSC) += -march=nocona - cflags-$(CONFIG_MCORE2) += -march=core2 - cflags-$(CONFIG_MATOM) += -march=atom - cflags-$(CONFIG_GENERIC_CPU) += -march=x86-64 -mtune=generic - KBUILD_CFLAGS += $(cflags-y) - - rustflags-$(CONFIG_MK8) += -Ctarget-cpu=k8 - rustflags-$(CONFIG_MPSC) += -Ctarget-cpu=nocona - rustflags-$(CONFIG_MCORE2) += -Ctarget-cpu=core2 - rustflags-$(CONFIG_MATOM) += -Ctarget-cpu=atom - rustflags-$(CONFIG_GENERIC_CPU) += -Ctarget-cpu=x86-64 -Ztune-cpu=generic - KBUILD_RUSTFLAGS += $(rustflags-y) + KBUILD_CFLAGS += -march=x86-64 -mtune=generic + KBUILD_RUSTFLAGS += -Ctarget-cpu=x86-64 -Ztune-cpu=generic KBUILD_CFLAGS += -mno-red-zone KBUILD_CFLAGS += -mcmodel=kernel
arch/x86/Makefile_32.cpu +1 -4
@@ -24,7 +24,6 @@ cflags-$(CONFIG_MK6) += -march=k6 # Please note, that patches that add -march=athlon-xp and friends are pointless. # They make zero difference whatsosever to performance at this time. cflags-$(CONFIG_MK7) += -march=athlon -cflags-$(CONFIG_MK8) += $(call cc-option,-march=k8,-march=athlon) cflags-$(CONFIG_MCRUSOE) += -march=i686 $(align) cflags-$(CONFIG_MEFFICEON) += -march=i686 $(call tune,pentium3) $(align) cflags-$(CONFIG_MWINCHIPC6) += $(call cc-option,-march=winchip-c6,-march=i586)
@@ -32,9 +31,7 @@ cflags-$(CONFIG_MWINCHIP3D) += $(call cc-option,-march=winchip2,-march=i586) cflags-$(CONFIG_MCYRIXIII) += $(call cc-option,-march=c3,-march=i486) $(align) cflags-$(CONFIG_MVIAC3_2) += $(call cc-option,-march=c3-2,-march=i686) cflags-$(CONFIG_MVIAC7) += -march=i686 -cflags-$(CONFIG_MCORE2) += -march=i686 $(call tune,core2) -cflags-$(CONFIG_MATOM) += $(call cc-option,-march=atom,$(call cc-option,-march=core2,-march=i686)) \ - $(call cc-option,-mtune=atom,$(call cc-option,-mtune=generic)) +cflags-$(CONFIG_MATOM) += -march=atom # AMD Elan support cflags-$(CONFIG_MELAN) += -march=i486
arch/x86/include/asm/vermagic.h +0 -4
@@ -15,8 +15,6 @@#define MODULE_PROC_FAMILY "586TSC "#elif definedCONFIG_M586MMX #define MODULE_PROC_FAMILY "586MMX " -#elif definedCONFIG_MCORE2 -#define MODULE_PROC_FAMILY "CORE2 "#elif definedCONFIG_MATOM #define MODULE_PROC_FAMILY "ATOM "#elif definedCONFIG_M686
@@ -33,8 +31,6 @@#define MODULE_PROC_FAMILY "K6 "#elif definedCONFIG_MK7 #define MODULE_PROC_FAMILY "K7 " -#elif definedCONFIG_MK8 -#define MODULE_PROC_FAMILY "K8 "#elif definedCONFIG_MELAN #define MODULE_PROC_FAMILY "ELAN "#elif definedCONFIG_MCRUSOE
drivers/misc/mei/Kconfig +1 -1
@@ -3,7 +3,7 @@ config INTEL_MEI tristate "Intel Management Engine Interface" depends on X86 && PCI - default GENERIC_CPU || MCORE2 || MATOM || X86_GENERIC + default X86_64 || MATOM help The Intel Management Engine (Intel ME) provides Manageability, Security and Media services for system containing Intel chipsets.
Signature · 1 line
2.39.5
PATCH v2 5/11 x86: add CONFIG_X86_64_NATIVE option
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
As a replacement for the obsole MK8/MPSC/MCORE2 configuration options, allow building a specialized kernel for the local CPU, which is useful for users building their own kernels, and does not require maintaining a list of possible CPU options.
Between -march=native and -mtune=native, I pick the former in order to give the best performance through the use of extra instructions, but at the cost of not being able to run on older CPUs at all. This creates a small risk of running into illegal instruction faults when the resulting binary ends up being run on a machine other than the one it was built on.
--- arch/x86/Kconfig.cpu | 14 ++++++++++++++ arch/x86/Makefile | 5 +++++ 2 files changed, 19 insertions(+)
arch/x86/Kconfig.cpu +14 -0
@@ -257,6 +257,20 @@ config X86_GENERIC This is really intended for distributors who need more generic optimizations. +config X86_64_NATIVE + bool "Build with -march=native optimization" + depends on X86_64 + help + Make it possible to have a slightly better optimized kernel for + the machine it is built on, by passing -march=native instead + the more generic -march=x86-64 option. This lets compilers + use extensions to the x86-64 instruction set that were not + present in the original AMD Opteron and Intel Pentium4 CPUs, + and schedule instructions for the pipeline model. + + Select this option only when building a kernel to run locally, + as it may be incompatible with any other processor. + # # Define implied options from the CPU selection here config X86_INTERNODE_CACHE_SHIFT
arch/x86/Makefile +5 -0
@@ -178,8 +178,13 @@ else # Use -mskip-rax-setup if supported. KBUILD_CFLAGS += $(call cc-option,-mskip-rax-setup) +ifdef CONFIG_X86_64_NATIVE + KBUILD_CFLAGS += -march=native + KBUILD_RUSTFLAGS += -Ctarget-cpu=native +else KBUILD_CFLAGS += -march=x86-64 -mtune=generic KBUILD_RUSTFLAGS += -Ctarget-cpu=x86-64 -Ztune-cpu=generic +endif KBUILD_CFLAGS += -mno-red-zone KBUILD_CFLAGS += -mcmodel=kernel
Signature · 1 line
2.39.5
Re: [PATCH v2 05/11] x86: add CONFIG_X86_64_NATIVE option
Hello.
Quoted 4 lines · Arnd Bergmann
As a replacement for the obsole MK8/MPSC/MCORE2 configuration options, allow building a specialized kernel for the local CPU, which is useful for users building their own kernels, and does not require maintaining a list of possible CPU options.
That potentially introduces problems. Namely compilers could apply auto-vectorization, which currently breaks the kernel. We probably need an additional patch like this: https://github.com/zen-kernel/zen-kernel/commit/95b7981ba2e5c86529de0e895c2d9e428aa3f7dc
Arnd Bergmann
maintainerRe: [PATCH v2 05/11] x86: add CONFIG_X86_64_NATIVE option
Quoted 8 lines · On Tue, Dec 10, 2024, at 20:05, [email protected] wrote:
Hello.
Quoted 4 lines · Arnd Bergmann
As a replacement for the obsole MK8/MPSC/MCORE2 configuration options, allow building a specialized kernel for the local CPU, which is useful for users building their own kernels, and does not require maintaining a list of possible CPU options.
Quoted 4 lines
That potentially introduces problems. Namely compilers could apply auto-vectorization, which currently breaks the kernel. We probably need an additional patch like this:
https://github.com/zen-kernel/zen-kernel/commit/95b7981ba2e5c86529de0e895c2d9e428aa3f7dc
I don't see how either -mno-avx2 or -fno-tree-vectorize would be needed here: avx2 is already turned off because of -mno-avx, and -ftree-vectorize is only enabled by default at -O3 level, which we don't use (and which doesn't add any instructions). There may be other flags that need to be disabled though.
With the flags we currently pass to the kernel, this is the difference in the gcc-14 -Q --help=target output between the x86-64 baseline and the -march=emeraldrapids, which is currently the most featureful:
a renamed from b +42 -42
@@ -12,24 +12,24 @@ -mabm [disabled] -maccumulate-outgoing-args [disabled] -maddress-mode= long - -madx [disabled] - -maes [disabled] + -madx [enabled] + -maes [enabled] -malign-data= compat -malign-double [disabled] -malign-functions= 0 -malign-jumps= 0 -malign-loops= 0 -malign-stringops [enabled] - -mamx-bf16 [disabled] + -mamx-bf16 [enabled] -mamx-complex [disabled] -mamx-fp16 [disabled] - -mamx-int8 [disabled] - -mamx-tile [disabled] + -mamx-int8 [enabled] + -mamx-tile [enabled] -mandroid [disabled] -mapx-features= none -mapx-inline-asm-use-gpr32 [disabled] -mapxf [disabled] - -march= x86-64 + -march= emeraldrapids -masm= att -mavx [disabled] -mavx10.1 -mavx10.1-256
@@ -62,27 +62,27 @@ -mavxvnniint16 [disabled] -mavxvnniint8 [disabled] -mbionic [disabled] - -mbmi [disabled] - -mbmi2 [disabled] + -mbmi [enabled] + -mbmi2 [enabled] -mbranch-cost=<0,5> 3 -mcall-ms2sysv-xlogues [disabled] -mcet-switch [disabled] -mcld [disabled] - -mcldemote [disabled] - -mclflushopt [disabled] - -mclwb [disabled] + -mcldemote [enabled] + -mclflushopt [enabled] + -mclwb [enabled] -mclzero [disabled] -mcmodel= kernel -mcmpccxadd [disabled] -mcpu= -mcrc32 [disabled] - -mcx16 [disabled] + -mcx16 [enabled] -mdaz-ftz [disabled] -mdirect-extern-access [enabled] -mdispatch-scheduler [disabled] -mdump-tune-features [disabled] - -menqcmd [disabled] - -mevex512 [disabled] + -menqcmd [enabled] + -mevex512 [enabled] -mf16c [disabled] -mfancy-math-387 [disabled] -mfentry [disabled]
@@ -94,17 +94,17 @@ -mforce-indirect-call [disabled] -mfp-ret-in-387 [disabled] -mfpmath= 387 - -mfsgsbase [disabled] + -mfsgsbase [enabled] -mfunction-return= keep -mfused-madd -ffp-contract=fast -mfxsr [enabled] -mgather -mtune-ctrl=use_gather -mgeneral-regs-only [disabled] - -mgfni [disabled] + -mgfni [enabled] -mglibc [enabled] -mhard-float [disabled] -mharden-sls= none - -mhle [disabled] + -mhle [enabled] -mhreset [disabled] -miamcu [disabled] -mieee-fp [enabled]
@@ -123,15 +123,15 @@ -mlong-double-64 [disabled] -mlong-double-80 [enabled] -mlwp [disabled] - -mlzcnt [disabled] + -mlzcnt [enabled] -mmanual-endbr [disabled] -mmemcpy-strategy= -mmemset-strategy= -mmitigate-rop [disabled] -mmmx [disabled] - -mmovbe [disabled] - -mmovdir64b [disabled] - -mmovdiri [disabled] + -mmovbe [enabled] + -mmovdir64b [enabled] + -mmovdiri [enabled] -mmove-max= 128 -mmpx [disabled] -mms-bitfields [disabled]
@@ -152,23 +152,23 @@ -mpc32 [disabled] -mpc64 [disabled] -mpc80 [disabled] - -mpclmul [disabled] + -mpclmul [enabled] -mpcommit [disabled] - -mpconfig [disabled] - -mpku [disabled] - -mpopcnt [disabled] + -mpconfig [enabled] + -mpku [enabled] + -mpopcnt [enabled] -mprefer-avx128 -mprefer-vector-width=128 -mprefer-vector-width= none -mpreferred-stack-boundary= 3 -mprefetchi [disabled] -mprefetchwt1 [disabled] - -mprfchw [disabled] - -mptwrite [disabled] + -mprfchw [enabled] + -mptwrite [enabled] -mpush-args [enabled] -mraoint [disabled] - -mrdpid [disabled] - -mrdrnd [disabled] - -mrdseed [disabled] + -mrdpid [enabled] + -mrdrnd [enabled] + -mrdseed [enabled] -mrecip [disabled] -mrecip= -mrecord-mcount [disabled]
@@ -178,11 +178,11 @@ -mrelax-cmpxchg-loop [disabled] -mrtd [disabled] -mrtm [disabled] - -msahf [disabled] + -msahf [enabled] -mscatter -mtune-ctrl=use_scatter - -mserialize [disabled] - -msgx [disabled] - -msha [disabled] + -mserialize [enabled] + -msgx [enabled] + -msha [enabled] -msha512 [disabled] -mshstk [disabled] -mskip-rax-setup [enabled]
@@ -212,11 +212,11 @@ -mtbm [disabled] -mtls-dialect= gnu -mtls-direct-seg-refs [enabled] - -mtsxldtrk [disabled] + -mtsxldtrk [enabled] -mtune-ctrl= -mtune= generic -muclibc [disabled] - -muintr [disabled] + -muintr [enabled] -munroll-only-small-loops [enabled] -musermsr [disabled] -mvaes [disabled]
@@ -224,15 +224,15 @@ -mvect8-ret-in-mem [disabled] -mvpclmulqdq [disabled] -mvzeroupper [enabled] - -mwaitpkg [disabled] - -mwbnoinvd [disabled] + -mwaitpkg [enabled] + -mwbnoinvd [enabled] -mwidekl [disabled] -mx32 [disabled] -mxop [disabled] - -mxsave [disabled] - -mxsavec [disabled] - -mxsaveopt [disabled] - -mxsaves [disabled] + -mxsave [enabled] + -mxsavec [enabled] + -mxsaveopt [enabled] + -mxsaves [enabled]
I don't know what most of them do, but the ones I looked up seem to be mainly integer operations.
Arnd
Re: [PATCH v2 05/11] x86: add CONFIG_X86_64_NATIVE option
Quoted 1 line · Arnd Bergmann
-ftree-vectorize is only enabled by default at -O3 level
You maybe missed it, but vectorization is enabled at -O2 level since GCC 12. https://www.phoronix.com/news/GCC-12-Auto-Vec-O2
Same goes for clang, it pretty much always had vectorized on -O2, iirc.
Quoted 1 line
avx2 is already turned off because of -mno-avx,
Hmm, I'm not sure. But if we look at existing KBUILD_RUSTFLAGS below, it has both -avx and -avx2.
Re: [PATCH v2 05/11] x86: add CONFIG_X86_64_NATIVE option
In reply to Arnd BergmannQuoted 7 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
As a replacement for the obsole MK8/MPSC/MCORE2 configuration options, allow building a specialized kernel for the local CPU, which is useful for users building their own kernels, and does not require maintaining a list of possible CPU options.
Quoted 6 lines
Between -march=native and -mtune=native, I pick the former in order to give the best performance through the use of extra instructions, but at the cost of not being able to run on older CPUs at all. This creates a small risk of running into illegal instruction faults when the resulting binary ends up being run on a machine other than the one it was built on.
Setting this option makes the kernel build non-reproducible (as it'll build differently on different systems).
I personally think this is a little questionable, as opposed to having well-defined optimization levels that are tested and supported and selecting one of those with a make nativeconfig. But if this does get added:
- Could you please document in Documentation/kbuild/reproducible-builds.rst that this option should not be set if you want reproducible builds?
- Could you add something similar to the config options LTO uses, to make allyesconfig and allmodconfig turn this back *off*?
PATCH v2 6/11 x86: remove HIGHMEM64G support
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The HIGHMEM64G support was added in linux-2.3.25 to support (then) high-end Pentium Pro and Pentium III Xeon servers with more than 4GB of addressing, NUMA and PCI-X slots started appearing.
I have found no evidence of this ever being used in regular dual-socket servers or consumer devices, all the users seem obsolete these days, even by i386 standards:
- Support for NUMA servers (NUMA-Q, IBM x440, unisys) was already removed ten years ago.
- 4+ socket non-NUMA servers based on Intel 450GX/450NX, HP F8 and ServerWorks ServerSet/GrandChampion could theoretically still work with 8GB, but these were exceptionally rare even 20 years ago and would have usually been equipped with than the maximum amount of RAM.
- Some SKUs of the Celeron D from 2004 had 64-bit mode fused off but could still work in a Socket 775 mainboard designed for the later Core 2 Duo and 8GB. Apparently most BIOSes at the time only allowed 64-bit CPUs.
- In the early days of x86-64 hardware, there was sometimes the need to run a 32-bit kernel to work around bugs in the hardware drivers, or in the syscall emulation for 32-bit userspace. This likely still works but there should never be a need for this any more.
PAE mode is still required to get access to the 'NX' bit on Atom 'Pentium M' and 'Core Duo' CPUs.
--- Documentation/admin-guide/kdump/kdump.rst | 4 -- Documentation/arch/x86/usb-legacy-support.rst | 11 +---- arch/x86/Kconfig | 46 +++---------------- arch/x86/configs/xen.config | 2 - arch/x86/include/asm/page_32_types.h | 4 +- arch/x86/mm/init_32.c | 9 +--- 6 files changed, 11 insertions(+), 65 deletions(-)
Documentation/admin-guide/kdump/kdump.rst +0 -4
@@ -180,10 +180,6 @@ Dump-capture kernel config options (Arch Dependent, i386 and x86_64) 1) On i386, enable high memory support under "Processor type and features":: - CONFIG_HIGHMEM64G=y - - or:: - CONFIG_HIGHMEM4G 2) With CONFIG_SMP=y, usually nr_cpus=1 need specified on the kernel
Documentation/arch/x86/usb-legacy-support.rst +1 -10
@@ -20,11 +20,7 @@ It has several drawbacks, though: features (wheel, extra buttons, touchpad mode) of the real PS/2 mouse may not be available. -2) If CONFIG_HIGHMEM64G is enabled, the PS/2 mouse emulation can cause - system crashes, because the SMM BIOS is not expecting to be in PAE mode. - The Intel E7505 is a typical machine where this happens. - -3) If AMD64 64-bit mode is enabled, again system crashes often happen, +2) If AMD64 64-bit mode is enabled, again system crashes often happen, because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The BIOS manufacturers only test with Windows, and Windows doesn't do 64-bit yet.
@@ -38,11 +34,6 @@ Problem 1) compiled-in, too. Problem 2) - can currently only be solved by either disabling HIGHMEM64G - in the kernel config or USB Legacy support in the BIOS. A BIOS update - could help, but so far no such update exists. - -Problem 3) is usually fixed by a BIOS update. Check the board manufacturers web site. If an update is not available, disable USB Legacy support in the BIOS. If this alone doesn't help, try also adding
arch/x86/Kconfig +6 -40
67 lines not on this page · raw message
arch/x86/configs/xen.config +0 -2
@@ -1,6 +1,4 @@ # global x86 required specific stuff -# On 32-bit HIGHMEM4G is not allowed -CONFIG_HIGHMEM64G=y CONFIG_64BIT=y # These enable us to allow some of the
arch/x86/include/asm/page_32_types.h +2 -2
@@ -11,8 +11,8 @@* a virtual address space of one gigabyte, which limits the * amount of physical memory you can use to about 950MB. * -* If you want more physical memory than this then see the CONFIG_HIGHMEM4G -* and CONFIG_HIGHMEM64G options in the kernel configuration. +* If you want more physical memory than this then see the CONFIG_VMSPLIT_2G +* and CONFIG_HIGHMEM4G options in the kernel configuration. */ #define __PAGE_OFFSET_BASE _AC(CONFIG_PAGE_OFFSET, UL)#define __PAGE_OFFSET __PAGE_OFFSET_BASE
arch/x86/mm/init_32.c +2 -7
@@ -582,7 +582,7 @@ static void __init lowmem_pfn_init(void)"only %luMB highmem pages available, ignoring highmem size of %luMB!\n" #define MSG_HIGHMEM_TRIMMED \ -"Warning: only 4GB will be used. Use a HIGHMEM64G enabled kernel!\n" +"Warning: only 4GB will be used. Support for for CONFIG_HIGHMEM64G was removed!\n" /* * We have more RAM than fits into lowmem - we try to put it into * highmem, also taking the highmem=x boot parameter into account:
@@ -606,18 +606,13 @@ static void __init highmem_pfn_init(void)#ifndef CONFIG_HIGHMEM /* Maximum memory usable is what is directly addressable */ printk (KERN_WARNING "Warning only %ldMB will be used.\n" ,MAXMEM >>20 ); -if (max_pfn >MAX_NONPAE_PFN ) -printk (KERN_WARNING "Use a HIGHMEM64G enabled kernel.\n" ); -else -printk (KERN_WARNING "Use a HIGHMEM enabled kernel.\n" ); +printk (KERN_WARNING "Use a HIGHMEM enabled kernel.\n" ); max_pfn =MAXMEM_PFN ;#else /* !CONFIG_HIGHMEM */ -#ifndef CONFIG_HIGHMEM64G if (max_pfn >MAX_NONPAE_PFN ) { max_pfn =MAX_NONPAE_PFN ; printk(KERN_WARNING MSG_HIGHMEM_TRIMMED); } -#endif /* !CONFIG_HIGHMEM64G */ #endif /* !CONFIG_HIGHMEM */ }
Signature · 1 line
2.39.5
PATCH v2 7/11 x86: drop SWIOTLB and PHYS_ADDR_T_64BIT for PAE
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
Since kernels with and without CONFIG_X86_PAE are now limited to the low 4GB of physical address space, there is no need to use either swiotlb or 64-bit phys_addr_t any more, so stop selecting these and fix up the build warnings from that.
--- arch/x86/Kconfig | 2 -- arch/x86/mm/pgtable.c | 5 +++-- include/linux/mm.h | 2 +- 3 files changed, 4 insertions(+), 5 deletions(-)
arch/x86/Kconfig +0 -2
@@ -1456,8 +1456,6 @@ config HIGHMEM config X86_PAE bool "PAE (Physical Address Extension) Support" depends on X86_32 && X86_HAVE_PAE - select PHYS_ADDR_T_64BIT - select SWIOTLB help PAE is required for NX support, and furthermore enables larger swapspace support for non-overcommit purposes. It
arch/x86/mm/pgtable.c +3 -2
@@ -765,11 +765,12 @@ int pud_set_huge(pud_t *pud, phys_addr_t addr, pgprot_t prot)int pmd_set_huge (pmd_t *pmd,phys_addr_t addr,pgprot_t prot) {u8 uniform; +struct resource res =DEFINE_RES_MEM (addr,PMD_SIZE );mtrr_type_lookup (addr, addr +PMD_SIZE , &uniform);if (!uniform) { -pr_warn_once ("%s: Cannot satisfy [mem %#010llx-%#010llx] with a huge-page mapping due to MTRR override.\n" , - __func__, addr, addr +PMD_SIZE ); +pr_warn_once ("%s: Cannot satisfy %pR with a huge-page mapping due to MTRR override.\n" , + __func__, &res);return 0 ; }
include/linux/mm.h +1 -1
@@ -99,7 +99,7 @@ extern int mmap_rnd_compat_bits __read_mostly;#ifndef DIRECT_MAP_PHYSMEM_END # ifdef MAX_PHYSMEM_BITS -# define DIRECT_MAP_PHYSMEM_END ((1ULL << MAX_PHYSMEM_BITS) - 1) +# define DIRECT_MAP_PHYSMEM_END (phys_addr_t)((1ULL << MAX_PHYSMEM_BITS) - 1)# else # define DIRECT_MAP_PHYSMEM_END (((phys_addr_t)-1)&~(1ULL<<63))# endif
Signature · 1 line
2.39.5
kernel test robot
build botRe: [PATCH v2 07/11] x86: drop SWIOTLB and PHYS_ADDR_T_64BIT for PAE
kernel test robot noticed "WARNING:at_mm/sparse.c:#sparse_init" on:
Hello,
kernel test robot noticed "WARNING:at_mm/sparse.c:#sparse_init" on:
commit: a20f815a6f361e18a0a2a9480b5a5340c5860c7f ("[PATCH v2 07/11] x86: drop SWIOTLB and PHYS_ADDR_T_64BIT for PAE")
url: https://github.com/intel-lab-lkp/linux/commits/Arnd-Bergmann/x86-Kconfig-Geode-CPU-has-cmpxchg8b/20241210-225443
base: https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git f576cfc3d433316990802cd521ddea645eb3971b patch link: https://lore.kernel.org/all/[email protected]/
patch subject: [PATCH v2 07/11] x86: drop SWIOTLB and PHYS_ADDR_T_64BIT for PAE
in testcase: boot
config: i386-randconfig-001-20241213
compiler: gcc-12
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+------------------------------------------------+------------+------------+ | | 620a8e2d2b | a20f815a6f | +------------------------------------------------+------------+------------+ | WARNING:at_mm/sparse.c:#sparse_init | 0 | 12 | | EIP:sparse_init | 0 | 12 | | BUG:kernel_NULL_pointer_dereference,address | 0 | 12 | | Oops | 0 | 12 | | Kernel_panic-not_syncing:Fatal_exception | 0 | 12 | +------------------------------------------------+------------+------------+
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-lkp/[email protected]
[ 0.068283][ T0] ------------[ cut here ]------------ [ 0.068644][ T0] WARNING: CPU: 0 PID: 0 at mm/sparse.c:149 sparse_init (mm/sparse.c:149 mm/sparse.c:227 mm/sparse.c:268 mm/sparse.c:565) [ 0.069169][ T0] Modules linked in: [ 0.069424][ T0] CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 6.13.0-rc2-00153-ga20f815a6f36 #1 55e1ad47972e976fedebf027f6853ef569639c5a [ 0.070285][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 [ 0.070972][ T0] EIP: sparse_init (mm/sparse.c:149 mm/sparse.c:227 mm/sparse.c:268 mm/sparse.c:565) [ 0.071277][ T0] Code: 85 d2 74 d1 8b 0d 44 5f 72 b2 85 c9 7e 1c 89 54 24 08 31 c0 31 d2 89 44 24 0c 89 54 24 04 c7 04 24 d8 e5 04 b2 e8 55 ea a2 fe <0f> 0b eb a7 90 8b 0d 80 16 e7 b2 31 d2 8d b4 26 00 00 00 00 90 83 All code ======== 0: 85 d2 test %edx,%edx 2: 74 d1 je 0xffffffffffffffd5 4: 8b 0d 44 5f 72 b2 mov -0x4d8da0bc(%rip),%ecx # 0xffffffffb2725f4e a: 85 c9 test %ecx,%ecx c: 7e 1c jle 0x2a e: 89 54 24 08 mov %edx,0x8(%rsp) 12: 31 c0 xor %eax,%eax 14: 31 d2 xor %edx,%edx 16: 89 44 24 0c mov %eax,0xc(%rsp) 1a: 89 54 24 04 mov %edx,0x4(%rsp) 1e: c7 04 24 d8 e5 04 b2 movl $0xb204e5d8,(%rsp) 25: e8 55 ea a2 fe call 0xfffffffffea2ea7f 2a:* 0f 0b ud2 <-- trapping instruction 2c: eb a7 jmp 0xffffffffffffffd5 2e: 90 nop 2f: 8b 0d 80 16 e7 b2 mov -0x4d18e980(%rip),%ecx # 0xffffffffb2e716b5 35: 31 d2 xor %edx,%edx
37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
3e: 90 nop
3f: 83 .byte 0x83
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2 2: eb a7 jmp 0xffffffffffffffab 4: 90 nop 5: 8b 0d 80 16 e7 b2 mov -0x4d18e980(%rip),%ecx # 0xffffffffb2e7168b b: 31 d2 xor %edx,%edx d: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi 14: 90 nop 15: 83 .byte 0x83 [ 0.072580][ T0] EAX: 00000000 EBX: b218feb4 ECX: 00000000 EDX: 0000009f [ 0.073047][ T0] ESI: b218febc EDI: 00000000 EBP: b218fecc ESP: b218feb4 [ 0.073513][ T0] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: febc EFLAGS: 00210046 [ 0.074016][ T0] CR0: 80050033 CR2: 00000000 CR3: 02773000 CR4: 00000090 [ 0.074492][ T0] Call Trace: [ 0.074709][ T0] ? show_regs (arch/x86/kernel/dumpstack.c:479) [ 0.074989][ T0] ? sparse_init (mm/sparse.c:149 mm/sparse.c:227 mm/sparse.c:268 mm/sparse.c:565) [ 0.075283][ T0] ? __warn (kernel/panic.c:748) [ 0.075550][ T0] ? sparse_init (mm/sparse.c:149 mm/sparse.c:227 mm/sparse.c:268 mm/sparse.c:565) [ 0.075845][ T0] ? sparse_init (mm/sparse.c:149 mm/sparse.c:227 mm/sparse.c:268 mm/sparse.c:565) [ 0.076140][ T0] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 0.076437][ T0] ? sparse_init (mm/sparse.c:149 mm/sparse.c:227 mm/sparse.c:268 mm/sparse.c:565) [ 0.076731][ T0] ? early_fixup_exception (arch/x86/mm/extable.c:415) [ 0.077081][ T0] ? early_idt_handler_common (arch/x86/kernel/head_32.S:352) [ 0.077450][ T0] ? register_lock_class (kernel/locking/lockdep.c:195 kernel/locking/lockdep.c:1322) [ 0.077799][ T0] ? sparse_init (mm/sparse.c:149 mm/sparse.c:227 mm/sparse.c:268 mm/sparse.c:565) [ 0.078113][ T0] ? native_flush_tlb_global (arch/x86/include/asm/irqflags.h:154 arch/x86/mm/tlb.c:1225) [ 0.078480][ T0] paging_init (arch/x86/mm/init_32.c:685) [ 0.078759][ T0] native_pagetable_init (arch/x86/mm/init_32.c:481) [ 0.079101][ T0] ? _printk (kernel/printk/printk.c:2461) [ 0.079367][ T0] ? dma_contiguous_reserve (kernel/dma/contiguous.c:250) [ 0.079722][ T0] setup_arch (arch/x86/kernel/setup.c:1130) [ 0.080011][ T0] start_kernel (init/main.c:924 (discriminator 3)) [ 0.080301][ T0] ? load_ucode_bsp (arch/x86/kernel/cpu/microcode/core.c:135) [ 0.080622][ T0] i386_start_kernel (??:?) [ 0.080936][ T0] startup_32_smp (arch/x86/kernel/head_32.S:292) [ 0.081247][ T0] irq event stamp: 0 [ 0.081500][ T0] hardirqs last enabled at (0): 0x0 [ 0.081922][ T0] hardirqs last disabled at (0): 0x0 [ 0.082349][ T0] softirqs last enabled at (0): 0x0 [ 0.082771][ T0] softirqs last disabled at (0): 0x0 [ 0.083193][ T0] ---[ end trace 0000000000000000 ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241220/[email protected]
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Arnd Bergmann
maintainerRe: [PATCH v2 07/11] x86: drop SWIOTLB and PHYS_ADDR_T_64BIT for PAE
Quoted 7 lines · kernel test robot
config: i386-randconfig-001-20241213
compiler: gcc-12
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G(please refer to attached dmesg/kmsg for entire log/backtrace)
I haven't been able to figure this out, apparently something goes wrong on a KVM guest that has more than 32-bit of addressing (RAM+MMIO) when it uses a 32-bit phys_addr_t.
I changed the patch now to only drop SWIOTLB, not PHYS_ADDR_T_64BIT.
Arnd
PATCH v2 8/11 x86: drop support for CONFIG_HIGHPTE
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
With the maximum amount of RAM now 4GB, there is very little point to still have PTE pages in highmem. Drop this for simplification.
The only other architecture supporting HIGHPTE is 32-bit arm, and once that feature is removed as well, the highpte logic can be dropped from common code as well.
--- .../admin-guide/kernel-parameters.txt | 7 ----- arch/x86/Kconfig | 9 ------- arch/x86/include/asm/pgalloc.h | 5 ---- arch/x86/mm/pgtable.c | 27 +------------------ 4 files changed, 1 insertion(+), 47 deletions(-)
Documentation/admin-guide/kernel-parameters.txt +0 -7
@@ -7341,13 +7341,6 @@ 16 - SIGBUS faults Example: user_debug=31 - userpte= - [X86,EARLY] Flags controlling user PTE allocations. - - nohigh = do not allocate PTE pages in - HIGHMEM regardless of setting - of CONFIG_HIGHPTE. - vdso= [X86,SH,SPARC] On X86_32, this is an alias for vdso32=. Otherwise:
arch/x86/Kconfig +0 -9
@@ -1621,15 +1621,6 @@ config X86_PMEM_LEGACY Say Y if unsure. -config HIGHPTE - bool "Allocate 3rd-level pagetables from highmem" - depends on HIGHMEM - help - The VM uses one page table entry for each page of physical memory. - For systems with a lot of RAM, this can be wasteful of precious - low memory. Setting this option will put user-space page table - entries in high memory. - config X86_CHECK_BIOS_CORRUPTION bool "Check for low memory corruption" help
arch/x86/include/asm/pgalloc.h +0 -5
@@ -29,11 +29,6 @@ static inline void paravirt_release_pud(unsigned long pfn) {}static inline void paravirt_release_p4d (unsigned long pfn) {}#endif -/* -* Flags to use when allocating a user page table page. -*/ -extern gfp_t __userpte_alloc_gfp; -#ifdef CONFIG_MITIGATION_PAGE_TABLE_ISOLATION /* * Instead of one PGD, we acquire two PGDs. Being order-1, it is
arch/x86/mm/pgtable.c +1 -26
@@ -12,12 +12,6 @@ phys_addr_t physical_mask __ro_after_init = (1ULL << __PHYSICAL_MASK_SHIFT) - 1;EXPORT_SYMBOL (physical_mask);#endif -#ifdef CONFIG_HIGHPTE -#define PGTABLE_HIGHMEM __GFP_HIGHMEM -#else -#define PGTABLE_HIGHMEM 0 -#endif -#ifndef CONFIG_PARAVIRT static inline void paravirt_tlb_remove_table (struct mmu_gather *tlb,void *table)
@@ -26,29 +20,10 @@ void paravirt_tlb_remove_table(struct mmu_gather *tlb, void *table) }#endif -gfp_t __userpte_alloc_gfp =GFP_PGTABLE_USER |PGTABLE_HIGHMEM ; -pgtable_t pte_alloc_one (struct mm_struct *mm) { -return __pte_alloc_one (mm, __userpte_alloc_gfp); -} - -static int __init setup_userpte (char *arg) -{ -if (!arg) -return -EINVAL ; - -/* -* "userpte=nohigh" disables allocation of user pagetables in -* high memory. -*/ -if (strcmp (arg,"nohigh" ) ==0 ) - __userpte_alloc_gfp &= ~__GFP_HIGHMEM; -else -return -EINVAL ; -return 0 ; +return __pte_alloc_one (mm,GFP_PGTABLE_USER ); } -early_param ("userpte" , setup_userpte);void ___pte_free_tlb (struct mmu_gather *tlb,struct page *pte) {
Signature · 1 line
2.39.5
PATCH v2 9/11 x86: document X86_INTEL_MID as 64-bit-only
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The X86_INTEL_MID code was originally introduced for the 32-bit Moorestown/Medfield/Clovertrail platform, later the 64-bit Merrifield/Moorefield variants were added, but the final Morganfield 14nm platform was canceled before it hit the market.
To help users understand what the option actually refers to, update the help text, and add a dependency on 64-bit kernels.
Ferry confirmed that all the hardware can run 64-bit kernels these days, but is still testing 32-bit kernels on the Intel Edison board, so this remains possible, but is guarded by a CONFIG_EXPERT dependency now, to gently push remaining users towards using CONFIG_64BIT.
--- arch/x86/Kconfig | 50 ++++++++++++++++++++++++++++-------------------- 1 file changed, 29 insertions(+), 21 deletions(-)
arch/x86/Kconfig +29 -21
@@ -544,12 +544,12 @@ config X86_EXTENDED_PLATFORM RDC R-321x SoC SGI 320/540 (Visual Workstation) STA2X11-based (e.g. Northville) - Moorestown MID devices 64-bit platforms (CONFIG_64BIT=y): Numascale NumaChip ScaleMP vSMP SGI Ultraviolet + Merrifield/Moorefield MID devices If you have one of these systems, or if you want to build a generic distribution kernel, say Y here - otherwise say N.
@@ -594,8 +594,31 @@ config X86_UV This option is needed in order to support SGI Ultraviolet systems. If you don't have one of these, you should say N here. -# Following is an alphabetically sorted list of 32 bit extended platforms -# Please maintain the alphabetic order if and when there are additions +config X86_INTEL_MID + bool "Intel Z34xx/Z35xx MID platform support" + depends on X86_EXTENDED_PLATFORM + depends on X86_PLATFORM_DEVICES + depends on PCI + depends on X86_64 || (EXPERT && PCI_GOANY) + depends on X86_IO_APIC + select I2C + select DW_APB_TIMER + select INTEL_SCU_PCI + help + Select to build a kernel capable of supporting 64-bit Intel MID + (Mobile Internet Device) platform systems which do not have + the PCI legacy interfaces. + + The only supported devices are the 22nm Merrified (Z34xx) + and Moorefield (Z35xx) SoC used in the Intel Edison board and + a small number of Android devices such as the Asus Zenfone 2, + Asus FonePad 8 and Dell Venue 7. + + If you are building for a PC class system or non-MID tablet + SoCs like Bay Trail (Z36xx/Z37xx), say N here. + + Intel MID platforms are based on an Intel processor and chipset which + consume less power than most of the x86 derivatives. config X86_GOLDFISH bool "Goldfish (Virtual Platform)"
@@ -605,6 +628,9 @@ config X86_GOLDFISH for Android development. Unless you are building for the Android Goldfish emulator say N here. +# Following is an alphabetically sorted list of 32 bit extended platforms +# Please maintain the alphabetic order if and when there are additions + config X86_INTEL_CE bool "CE4100 TV platform" depends on PCI
@@ -620,24 +646,6 @@ config X86_INTEL_CE This option compiles in support for the CE4100 SOC for settop boxes and media devices. -config X86_INTEL_MID - bool "Intel MID platform support" - depends on X86_EXTENDED_PLATFORM - depends on X86_PLATFORM_DEVICES - depends on PCI - depends on X86_64 || (PCI_GOANY && X86_32) - depends on X86_IO_APIC - select I2C - select DW_APB_TIMER - select INTEL_SCU_PCI - help - Select to build a kernel capable of supporting Intel MID (Mobile - Internet Device) platform systems which do not have the PCI legacy - interfaces. If you are building for a PC class system say N here. - - Intel MID platforms are based on an Intel processor and chipset which - consume less power than most of the x86 derivatives. - config X86_INTEL_QUARK bool "Intel Quark platform support" depends on X86_32
Signature · 1 line
2.39.5
PATCH v2 10/11 x86: remove old STA2x11 support
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
ST ConneXt STA2x11 was an interface chip for Atom E6xx processors, using a number of components usually found on Arm SoCs. Most of this was merged upstream, but it was never complete enough to actually work and has been abandoned for many years.
We already had an agreement on removing it in 2022, but nobody ever submitted the patch to do it.
Without STA2x11, the CONFIG_X86_32_NON_STANDARD no longer has any use.
--- arch/x86/Kconfig | 32 +---- arch/x86/include/asm/sta2x11.h | 13 -- arch/x86/pci/Makefile | 2 - arch/x86/pci/sta2x11-fixup.c | 233 --------------------------------- 4 files changed, 3 insertions(+), 277 deletions(-) delete mode 100644 arch/x86/include/asm/sta2x11.h delete mode 100644 arch/x86/pci/sta2x11-fixup.c
arch/x86/Kconfig +3 -29
@@ -543,7 +543,6 @@ config X86_EXTENDED_PLATFORM AMD Elan RDC R-321x SoC SGI 320/540 (Visual Workstation) - STA2X11-based (e.g. Northville) 64-bit platforms (CONFIG_64BIT=y): Numascale NumaChip
@@ -727,18 +726,6 @@ config X86_RDC321X as R-8610-(G). If you don't have one of these chips, you should say N here. -config X86_32_NON_STANDARD - bool "Support non-standard 32-bit SMP architectures" - depends on X86_32 && SMP - depends on X86_EXTENDED_PLATFORM - help - This option compiles in the STA2X11 default - subarchitecture. It is intended for a generic binary - kernel. If you select them all, kernel will probe it one by - one and will fallback to default. - -# Alphabetically sorted list of Non standard 32 bit platforms - config X86_SUPPORTS_MEMORY_FAILURE def_bool y # MCE code calls memory_failure():
@@ -748,19 +735,6 @@ config X86_SUPPORTS_MEMORY_FAILURE depends on X86_64 || !SPARSEMEM select ARCH_SUPPORTS_MEMORY_FAILURE -config STA2X11 - bool "STA2X11 Companion Chip Support" - depends on X86_32_NON_STANDARD && PCI - select SWIOTLB - select MFD_STA2X11 - select GPIOLIB - help - This adds support for boards based on the STA2X11 IO-Hub, - a.k.a. "ConneXt". The chip is used in place of the standard - PC chipset, so all "standard" peripherals are missing. If this - option is selected the kernel will still be able to boot on - standard PC machines. - config X86_32_IRIS tristate "Eurobraille/Iris poweroff module" depends on X86_32
@@ -1098,7 +1072,7 @@ config UP_LATE_INIT config X86_UP_APIC bool "Local APIC support on uniprocessors" if !PCI_MSI default PCI_MSI - depends on X86_32 && !SMP && !X86_32_NON_STANDARD + depends on X86_32 && !SMP help A local APIC (Advanced Programmable Interrupt Controller) is an integrated interrupt controller in the CPU. If you have a single-CPU
@@ -1123,7 +1097,7 @@ config X86_UP_IOAPIC config X86_LOCAL_APIC def_bool y - depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI + depends on X86_64 || SMP || X86_UP_APIC || PCI_MSI select IRQ_DOMAIN_HIERARCHY config ACPI_MADT_WAKEUP
@@ -1583,7 +1557,7 @@ config ARCH_FLATMEM_ENABLE config ARCH_SPARSEMEM_ENABLE def_bool y - depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD + depends on X86_64 || NUMA || X86_32 select SPARSEMEM_STATIC if X86_32 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
arch/x86/include/asm/sta2x11.h deleted +0 -13
@@ -1,13 +0,0 @@ -/* SPDX-License-Identifier: GPL-2.0 */ -/* -* Header file for STMicroelectronics ConneXt (STA2X11) IOHub -*/ -#ifndef __ASM_STA2X11_H -#define __ASM_STA2X11_H - -#include <linux/pci.h> - -/* This needs to be called from the MFD to configure its sub-devices */ -struct sta2x11_instance *sta2x11_get_instance (struct pci_dev *pdev); - -#endif /* __ASM_STA2X11_H */
arch/x86/pci/Makefile +0 -2
@@ -12,8 +12,6 @@ obj-$(CONFIG_X86_INTEL_CE) += ce4100.o obj-$(CONFIG_ACPI) += acpi.o obj-y += legacy.o irq.o -obj-$(CONFIG_STA2X11) += sta2x11-fixup.o - obj-$(CONFIG_X86_NUMACHIP) += numachip.o obj-$(CONFIG_X86_INTEL_MID) += intel_mid_pci.o
arch/x86/pci/sta2x11-fixup.c deleted +0 -233
233 lines not on this page · raw message
Signature · 1 line
2.39.5
Re: [PATCH v2 10/11] x86: remove old STA2x11 support
Quoted 8 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
ST ConneXt STA2x11 was an interface chip for Atom E6xx processors, using a number of components usually found on Arm SoCs. Most of this was merged upstream, but it was never complete enough to actually work and has been abandoned for many years.
Quoted 8 lines
We already had an agreement on removing it in 2022, but nobody ever submitted the patch to do it.
Without STA2x11, the
CONFIG_X86_32_NON_STANDARDno longer has any use.
Hmm... Haven't you got a tag for (at least) this one?
Signature · 2 lines
With Best Regards, Andy Shevchenko
PATCH v2 11/11 x86: Move platforms to Kconfig.platforms
In reply to Arnd BergmannFrom: Arnd Bergmann <[email protected]>
The x86 platform options in Kconfig are rather confusing, as they are a mix of options that just control visibility of drivers and those that are fundamental to the operation, with some of the code in arch/x86/platforms and other code in drivers/platform/x86, and the options listed in various places in arch/x86/Kconfig.
Make this a little more consistent by moving all options that control a platform from arch/x86/Kconfig to arch/x86/Kconfig.platforms and put them into a submenu.
--- arch/x86/Kconfig | 363 +------------------------------------ arch/x86/Kconfig.platforms | 361 ++++++++++++++++++++++++++++++++++++ 2 files changed, 363 insertions(+), 361 deletions(-) create mode 100644 arch/x86/Kconfig.platforms
arch/x86/Kconfig +2 -361
@@ -526,205 +526,7 @@ config X86_FRED ring transitions and exception/interrupt handling if the system supports it. -config X86_EXTENDED_PLATFORM - bool "Support for extended (non-PC) x86 platforms" - default y - help - If you disable this option then the kernel will only support - standard PC platforms. (which covers the vast majority of - systems out there.) - - If you enable this option then you'll be able to select support - for the following non-PC x86 platforms, depending on the value of - CONFIG_64BIT. - - 32-bit platforms (CONFIG_64BIT=n): - Goldfish (Android emulator) - AMD Elan - RDC R-321x SoC - SGI 320/540 (Visual Workstation) - - 64-bit platforms (CONFIG_64BIT=y): - Numascale NumaChip - ScaleMP vSMP - SGI Ultraviolet - Merrifield/Moorefield MID devices - - If you have one of these systems, or if you want to build a - generic distribution kernel, say Y here - otherwise say N. - -# This is an alphabetically sorted list of 64 bit extended platforms -# Please maintain the alphabetic order if and when there are additions -config X86_NUMACHIP - bool "Numascale NumaChip" - depends on X86_64 - depends on X86_EXTENDED_PLATFORM - depends on NUMA - depends on SMP - depends on X86_X2APIC - depends on PCI_MMCONFIG - help - Adds support for Numascale NumaChip large-SMP systems. Needed to - enable more than ~168 cores. - If you don't have one of these, you should say N here. - -config X86_VSMP - bool "ScaleMP vSMP" - select HYPERVISOR_GUEST - select PARAVIRT - depends on X86_64 && PCI - depends on X86_EXTENDED_PLATFORM - depends on SMP - help - Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is - supposed to run on these EM64T-based machines. Only choose this option - if you have one of these machines. - -config X86_UV - bool "SGI Ultraviolet" - depends on X86_64 - depends on X86_EXTENDED_PLATFORM - depends on NUMA - depends on EFI - depends on KEXEC_CORE - depends on X86_X2APIC - depends on PCI - help - This option is needed in order to support SGI Ultraviolet systems. - If you don't have one of these, you should say N here. - -config X86_INTEL_MID - bool "Intel Z34xx/Z35xx MID platform support" - depends on X86_EXTENDED_PLATFORM - depends on X86_PLATFORM_DEVICES - depends on PCI - depends on X86_64 || (EXPERT && PCI_GOANY) - depends on X86_IO_APIC - select I2C - select DW_APB_TIMER - select INTEL_SCU_PCI - help - Select to build a kernel capable of supporting 64-bit Intel MID - (Mobile Internet Device) platform systems which do not have - the PCI legacy interfaces. - - The only supported devices are the 22nm Merrified (Z34xx) - and Moorefield (Z35xx) SoC used in the Intel Edison board and - a small number of Android devices such as the Asus Zenfone 2, - Asus FonePad 8 and Dell Venue 7. - - If you are building for a PC class system or non-MID tablet - SoCs like Bay Trail (Z36xx/Z37xx), say N here. - - Intel MID platforms are based on an Intel processor and chipset which - consume less power than most of the x86 derivatives. - -config X86_GOLDFISH - bool "Goldfish (Virtual Platform)" - depends on X86_EXTENDED_PLATFORM - help - Enable support for the Goldfish virtual platform used primarily - for Android development. Unless you are building for the Android - Goldfish emulator say N here. - -# Following is an alphabetically sorted list of 32 bit extended platforms -# Please maintain the alphabetic order if and when there are additions - -config X86_INTEL_CE - bool "CE4100 TV platform" - depends on PCI - depends on PCI_GODIRECT - depends on X86_IO_APIC - depends on X86_32 - depends on X86_EXTENDED_PLATFORM - select X86_REBOOTFIXUPS - select OF - select OF_EARLY_FLATTREE - help - Select for the Intel CE media processor (CE4100) SOC. - This option compiles in support for the CE4100 SOC for settop - boxes and media devices. - -config X86_INTEL_QUARK - bool "Intel Quark platform support" - depends on X86_32 - depends on X86_EXTENDED_PLATFORM - depends on X86_PLATFORM_DEVICES - depends on X86_TSC - depends on PCI - depends on PCI_GOANY - depends on X86_IO_APIC - select IOSF_MBI - select INTEL_IMR - select COMMON_CLK - help - Select to include support for Quark X1000 SoC. - Say Y here if you have a Quark based system such as the Arduino - compatible Intel Galileo. - -config X86_INTEL_LPSS - bool "Intel Low Power Subsystem Support" - depends on X86 && ACPI && PCI - select COMMON_CLK - select PINCTRL - select IOSF_MBI - help - Select to build support for Intel Low Power Subsystem such as - found on Intel Lynxpoint PCH. Selecting this option enables - things like clock tree (common clock framework) and pincontrol - which are needed by the LPSS peripheral drivers. - -config X86_AMD_PLATFORM_DEVICE - bool "AMD ACPI2Platform devices support" - depends on ACPI - select COMMON_CLK - select PINCTRL - help - Select to interpret AMD specific ACPI device to platform device - such as I2C, UART, GPIO found on AMD Carrizo and later chipsets. - I2C and UART depend on COMMON_CLK to set clock. GPIO driver is - implemented under PINCTRL subsystem. - -config IOSF_MBI - tristate "Intel SoC IOSF Sideband support for SoC platforms" - depends on PCI - help - This option enables sideband register access support for Intel SoC - platforms. On these platforms the IOSF sideband is used in lieu of - MSR's for some register accesses, mostly but not limited to thermal - and power. Drivers may query the availability of this device to - determine if they need the sideband in order to work on these - platforms. The sideband is available on the following SoC products. - This list is not meant to be exclusive. - - BayTrail - - Braswell - - Quark - - You should say Y if you are running a kernel on one of these SoC's. - -config IOSF_MBI_DEBUG - bool "Enable IOSF sideband access through debugfs" - depends on IOSF_MBI && DEBUG_FS - help - Select this option to expose the IOSF sideband access registers (MCR, - MDR, MCRX) through debugfs to write and read register information from - different units on the SoC. This is most useful for obtaining device - state information for debug and analysis. As this is a general access - mechanism, users of this option would have specific knowledge of the - device they want to access. - - If you don't require the option or are in doubt, say N. - -config X86_RDC321X - bool "RDC R-321x SoC" - depends on X86_32 - depends on X86_EXTENDED_PLATFORM - select M486 - select X86_REBOOTFIXUPS - help - This option is needed for RDC R-321x system-on-chip, also known - as R-8610-(G). - If you don't have one of these chips, you should say N here. +source "arch/x86/Kconfig.platforms" config X86_SUPPORTS_MEMORY_FAILURE def_bool y
@@ -735,19 +537,6 @@ config X86_SUPPORTS_MEMORY_FAILURE depends on X86_64 || !SPARSEMEM select ARCH_SUPPORTS_MEMORY_FAILURE -config X86_32_IRIS - tristate "Eurobraille/Iris poweroff module" - depends on X86_32 - help - The Iris machines from EuroBraille do not have APM or ACPI support - to shut themselves down properly. A special I/O sequence is - needed to do so, which is what this module does at - kernel shutdown. - - This is only for Iris machines from EuroBraille. - - If unused, say N. - config SCHED_OMIT_FRAME_POINTER def_bool y prompt "Single-depth WCHAN output"
@@ -1275,39 +1064,6 @@ config X86_IOPL_IOPERM ability to disable interrupts from user space which would be granted if the hardware IOPL mechanism would be used. -config TOSHIBA - tristate "Toshiba Laptop support" - depends on X86_32 - help - This adds a driver to safely access the System Management Mode of - the CPU on Toshiba portables with a genuine Toshiba BIOS. It does - not work on models with a Phoenix BIOS. The System Management Mode - is used to set the BIOS and power saving options on Toshiba portables. - - For information on utilities to make use of this driver see the - Toshiba Linux utilities web site at: - <http://www.buzzard.org.uk/toshiba/>. - - Say Y if you intend to run this kernel on a Toshiba portable. - Say N otherwise. - -config X86_REBOOTFIXUPS - bool "Enable X86 board specific fixups for reboot" - depends on X86_32 - help - This enables chipset and/or board specific fixups to be done - in order to get reboot to work correctly. This is only needed on - some combinations of hardware and BIOS. The symptom, for which - this config is intended, is when reboot ends with a stalled/hung - system. - - Currently, the only fixup is for the Geode machines using - CS5530A and CS5536 chipsets and the RDC R-321x SoC. - - Say Y if you want to enable the fixup. Currently, it's safe to - enable this option even if you don't need it. - Say N otherwise. - config MICROCODE def_bool y depends on CPU_SUP_AMD || CPU_SUP_INTEL
@@ -2927,10 +2683,9 @@ config ISA_DMA_API Enables ISA-style DMA support for devices requiring such controllers. If unsure, say Y. -if X86_32 - config ISA bool "ISA support" + depends on X86_32 help Find out whether you have ISA slots on your motherboard. ISA is the name of a bus system, i.e. the way the CPU talks to the other stuff
@@ -2938,120 +2693,6 @@ config ISA (MCA) or VESA. ISA is an older system, now being displaced by PCI; newer boards don't support it. If you have ISA, say Y, otherwise N. -config SCx200 - tristate "NatSemi SCx200 support" - help - This provides basic support for National Semiconductor's - (now AMD's) Geode processors. The driver probes for the - PCI-IDs of several on-chip devices, so its a good dependency - for other scx200_* drivers. - - If compiled as a module, the driver is named scx200. - -config SCx200HR_TIMER - tristate "NatSemi SCx200 27MHz High-Resolution Timer Support" - depends on SCx200 - default y - help - This driver provides a clocksource built upon the on-chip - 27MHz high-resolution timer. Its also a workaround for - NSC Geode SC-1100's buggy TSC, which loses time when the - processor goes idle (as is done by the scheduler). The - other workaround is idle=poll boot option. - -config OLPC - bool "One Laptop Per Child support" - depends on !X86_PAE - select GPIOLIB - select OF - select OF_PROMTREE - select IRQ_DOMAIN - select OLPC_EC - help - Add support for detecting the unique features of the OLPC - XO hardware. - -config OLPC_XO1_PM - bool "OLPC XO-1 Power Management" - depends on OLPC && MFD_CS5535=y && PM_SLEEP - help - Add support for poweroff and suspend of the OLPC XO-1 laptop. - -config OLPC_XO1_RTC - bool "OLPC XO-1 Real Time Clock" - depends on OLPC_XO1_PM && RTC_DRV_CMOS - help - Add support for the XO-1 real time clock, which can be used as a - programmable wakeup source. - -config OLPC_XO1_SCI - bool "OLPC XO-1 SCI extras" - depends on OLPC && OLPC_XO1_PM && GPIO_CS5535=y - depends on INPUT=y - select POWER_SUPPLY - help - Add support for SCI-based features of the OLPC XO-1 laptop: - - EC-driven system wakeups - - Power button - - Ebook switch - - Lid switch - - AC adapter status updates - - Battery status updates - -config OLPC_XO15_SCI - bool "OLPC XO-1.5 SCI extras" - depends on OLPC && ACPI - select POWER_SUPPLY - help - Add support for SCI-based features of the OLPC XO-1.5 laptop: - - EC-driven system wakeups - - AC adapter status updates - - Battery status updates - -config GEODE_COMMON - bool - -config ALIX - bool "PCEngines ALIX System Support (LED setup)" - select GPIOLIB - select GEODE_COMMON - help - This option enables system support for the PCEngines ALIX. - At present this just sets up LEDs for GPIO control on - ALIX2/3/6 boards. However, other system specific setup should - get added here. - - Note: You must still enable the drivers for GPIO and LED support - (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs - - Note: You have to set alix.force=1 for boards with Award BIOS. - -config NET5501 - bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)" - select GPIOLIB - select GEODE_COMMON - help - This option enables system support for the Soekris Engineering net5501. - -config GEOS - bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)" - select GPIOLIB - select GEODE_COMMON - depends on DMI - help - This option enables system support for the Traverse Technologies GEOS. - -config TS5500 - bool "Technologic Systems TS-5500 platform support" - depends on MELAN - select CHECK_SIGNATURE - select NEW_LEDS - select LEDS_CLASS - help - This option enables system support for the Technologic Systems TS-5500. - -endif # X86_32 - config AMD_NB def_bool y depends on CPU_SUP_AMD && PCI
arch/x86/Kconfig.platforms new file +361 -0
361 lines not on this page · raw message
Signature · 1 line
2.39.5
Quoted 9 lines · Arnd Bergmann
From: Arnd Bergmann <[email protected]>
[sorry for sending a duplicate series, I just noticed I had
dropped lkml from cc when I sent this a few minutes ago]While looking at 32-bit arm cleanups, I came across some related topics on x86 and ended up making a series for those as well.
Quoted 7 lines
Primarily this is about running 32-bit kernels on 64-bit hardware, which usually works but should probably be discouraged more clearly by only providing support for features that are used on real 32-bit hardware:
I found only a few 2003-era high-end servers (HP DL740 and DL760 G2) that were the only possible remaining uses of HIGHMEM64G and BIGSMP after the removal of 32-bit NUMA machines in 2014. Similary, there is only
Similarly
Quoted 7 lines
one generation of hardware with support for VT-x. All these features can be removed without hurting users.
In the CPU selection, building a 32-bit kernel optimized for AMD K8 or Intel Core2 is anachronistic, so instead only 32-bit CPU types need to be offered as optimization targets. The "generic" target on 64-bit turned out to be slightly broken, so I included a fix for that as well.
...
Quoted 1 line
x86: document
X86_INTEL_MIDas 64-bit-only
Signature · 2 lines
With Best Regards, Andy Shevchenko