i386 Vmi config
RFC PATCH 2/24 i386 Vmi config
Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only are designed to run on modern hardware platforms. As such, they require a working APIC, and do not support some legacy functionality, including APM BIOS, ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of dropping ISA support). They also require a P6 series CPU.
arch/i386/Kconfig +36 -7
@@ -133,8 +133,33 @@ config X86_ES7000 Only choose this option if you have such a system, otherwise you should say N here. +config X86_VMI + bool "VMI architecture support" + help + This option builds a kernel designed to run on top of a virtual + machine interface layer (VMI). Say 'N' here unless you are + building a kernel to run inside a virtual machine. + endchoice +menu "VMI configurable support" + depends on X86_VMI + +config VMI_REQUIRE_HYPERVISOR + bool "Require hypervisor" + default n + help + This option forces the kernel to run with a hypervisor present. + The kernel will panic if booted on native hardware. + +config VMI_DEBUG + bool "VMI debugging" + default n + help + Provides extra debugging output and testing of VMI interfaces. + +endmenu + config ACPI_SRAT bool default y
@@ -270,7 +295,7 @@ config X86_VISWS_APIC config X86_MCE bool "Machine Check Exception" - depends on !X86_VOYAGER + depends on !(X86_VOYAGER) ---help--- Machine Check Exception support allows the processor to notify the kernel if it detects a problem (e.g. overheating, component failure).
@@ -307,6 +332,7 @@ config X86_MCE_P4THERMAL config TOSHIBA tristate "Toshiba Laptop support" + depends on !X86_VMI ---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
@@ -322,6 +348,7 @@ config TOSHIBA config I8K tristate "Dell laptop support" + depends on !X86_VMI ---help--- This adds a driver to safely access the System Management Mode of the CPU on the Dell Inspiron 8000. The System Management Mode
@@ -569,6 +596,7 @@ config HIGHPTE config MATH_EMULATION bool "Math emulation" + depends on !X86_VMI ---help--- Linux can emulate a math coprocessor (used for floating point operations) if you don't have one. 486DX and Pentium processors have
@@ -760,7 +788,7 @@ source kernel/power/Kconfig source "drivers/acpi/Kconfig" menu "APM (Advanced Power Management) BIOS Support" -depends on PM && !X86_VISWS +depends on PM && !(X86_VISWS || X86_VMI) config APM tristate "APM (Advanced Power Management) BIOS support"
@@ -930,8 +958,9 @@ config PCI choice prompt "PCI access mode" - depends on PCI && !X86_VISWS + depends on PCI && !(X86_VISWS || X86_VMI) default PCI_GOANY + ---help--- On PCI systems, the BIOS can be used to detect the PCI devices and determine their configuration. However, some old PCI motherboards
@@ -963,12 +992,12 @@ endchoice config PCI_BIOS bool - depends on !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY) + depends on !(X86_VISWS && X86_VMI) && PCI && (PCI_GOBIOS || PCI_GOANY) default y config PCI_DIRECT bool - depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS) + depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS || X86_VMI) default y config PCI_MMCONFIG
@@ -986,7 +1015,7 @@ config ISA_DMA_API config ISA bool "ISA support" - depends on !(X86_VOYAGER || X86_VISWS) + depends on !(X86_VOYAGER || X86_VISWS || X86_VMI) 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
@@ -1013,7 +1042,7 @@ config EISA source "drivers/eisa/Kconfig" config MCA - bool "MCA support" if !(X86_VISWS || X86_VOYAGER) + bool "MCA support" if !(X86_VISWS || X86_VOYAGER || X86_VMI) default y if X86_VOYAGER help MicroChannel Architecture is found in some IBM PS/2 machines and
arch/i386/Kconfig.cpu +5 -0
@@ -7,6 +7,7 @@ choice config M386 bool "386" + depends on !X86_VMI ---help--- This is the processor type of your CPU. This information is used for optimizing purposes. In order to compile a kernel that can run on
@@ -47,6 +48,7 @@ config M386 config M486 bool "486" + depends on !X86_VMI help Select this for a 486 series processor, either Intel or one of the compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,
@@ -55,6 +57,7 @@ config M486 config M586 bool "586/K5/5x86/6x86/6x86MX" + depends on !X86_VMI help Select this for an 586 or 686 series processor such as the AMD K5, the Cyrix 5x86, 6x86 and 6x86MX. This choice does not
@@ -62,12 +65,14 @@ config M586 config M586TSC bool "Pentium-Classic" + depends on !X86_VMI help Select this for a Pentium Classic processor with the RDTSC (Read Time Stamp Counter) instruction for benchmarking. config M586MMX bool "Pentium-MMX" + depends on !X86_VMI help Select this for a Pentium with the MMX graphics/multimedia extended instructions.
Quoted 14 lines · Zachary Amsden
===================================================================
arch/i386/Kconfig +7
-0@@ -133,8 +133,33 @@ config X86_ES7000 Only choose this option if you have such a system, otherwise you should say N here. +config X86_VMI + bool "VMI architecture support" + help + This option builds a kernel designed to run on top of a virtual + machine interface layer (VMI). Say 'N' here unless you are + building a kernel to run inside a virtual machine. +
Quoted 3 lines
endchoice
I think we should have a top level "Virtualisation" menu for VMI/Xen/vserver/openvz/etc. While this option might seem to belong here, it might be better for users to keep the configuration for the virtualisation approaches together.
Of course I'm not core team so don't go changing your patch, this is a point of discussion :)
Quoted 158 lines
arch/i386/Kconfig +18
-0+menu "VMI configurable support" + depends on X86_VMI + +config VMI_REQUIRE_HYPERVISOR + bool "Require hypervisor" + default n + help + This option forces the kernel to run with a hypervisor present. + The kernel will panic if booted on native hardware. + +config VMI_DEBUG + bool "VMI debugging" + default n + help + Provides extra debugging output and testing of VMI interfaces. + +endmenu +config
ACPI_SRAT
bool
default yarch/i386/Kconfig +0
-0@@ -270,7 +295,7 @@ config X86_VISWS_APICconfig
X86_MCE
bool "Machine Check Exception"arch/i386/Kconfig +1
-1- depends on !X86_VOYAGER + depends on !(X86_VOYAGER)---help---
Machine Check Exception support allows the processor to notify the kernel if it detects a problem (e.g. overheating, component failure).arch/i386/Kconfig +0
-0@@ -307,6 +332,7 @@ config X86_MCE_P4THERMALconfig TOSHIBA
tristate "Toshiba Laptop support"arch/i386/Kconfig +1
-0+ depends on !X86_VMI---help---
This adds a driver to safely access the System Management Mode of the CPU on Toshiba portables with a genuine Toshiba BIOS. It doesarch/i386/Kconfig +0
-0@@ -322,6 +348,7 @@ config TOSHIBAconfig I8K
tristate "Dell laptop support"arch/i386/Kconfig +1
-0+ depends on !X86_VMI---help---
This adds a driver to safely access the System Management Mode of the CPU on the Dell Inspiron 8000. The System Management Modearch/i386/Kconfig +0
-0@@ -569,6 +596,7 @@ config HIGHPTEconfig
MATH_EMULATION
bool "Math emulation"arch/i386/Kconfig +1
-0+ depends on !X86_VMI---help---
Linux can emulate a math coprocessor (used for floating point operations) if you don't have one. 486DX and Pentium processors havearch/i386/Kconfig +0
-0@@ -760,7 +788,7 @@ source kernel/power/Kconfigsource "
drivers/acpi/Kconfig"menu "APM (Advanced Power Management) BIOS Support"
arch/i386/Kconfig +1
-1-depends on PM && !X86_VISWS +depends on PM && !(X86_VISWS || X86_VMI)config APM
tristate "APM (Advanced Power Management) BIOS support"arch/i386/Kconfig +0
-0@@ -930,8 +958,9 @@ config PCIchoice
prompt "PCI access mode"arch/i386/Kconfig +1
-1- depends on PCI && !X86_VISWS + depends on PCI && !(X86_VISWS || X86_VMI)default
PCI_GOANY
+
---help---
On PCI systems, the BIOS can be used to detect the PCI devices and determine their configuration. However, some old PCI motherboardsarch/i386/Kconfig +0
-0@@ -963,12 +992,12 @@ endchoiceconfig
PCI_BIOS
boolarch/i386/Kconfig +1
-1- depends on !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY) + depends on !(X86_VISWS && X86_VMI) && PCI && (PCI_GOBIOS || PCI_GOANY)default y
config
PCI_DIRECT
boolarch/i386/Kconfig +1
-1- depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS) + depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS || X86_VMI)default y
config
PCI_MMCONFIGarch/i386/Kconfig +0
-0@@ -986,7 +1015,7 @@ config ISA_DMA_APIconfig ISA
bool "ISA support"arch/i386/Kconfig +1
-1- depends on !(X86_VOYAGER || X86_VISWS) + depends on !(X86_VOYAGER || X86_VISWS || X86_VMI)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 stuffarch/i386/Kconfig +0
-0@@ -1013,7 +1042,7 @@ config EISAsource "
drivers/eisa/Kconfig"config MCA
arch/i386/Kconfig +1
-1- bool "MCA support" if !(X86_VISWS || X86_VOYAGER) + bool "MCA support" if !(X86_VISWS || X86_VOYAGER || X86_VMI)default y if
X86_VOYAGER
help
MicroChannel Architecture is found in some IBM PS/2 machines and
Index: linux-2.6.16-rc5/arch/i386/Kconfig.cpu
===================================================================arch/i386/Kconfig.cpu +0
-0@@ -7,6 +7,7 @@ choiceconfig M386
bool "386"arch/i386/Kconfig.cpu +1
-0+ depends on !X86_VMI---help---
This is the processor type of your CPU. This information is used for optimizing purposes. In order to compile a kernel that can run onarch/i386/Kconfig.cpu +0
-0@@ -47,6 +48,7 @@ config M386config M486
bool "486"arch/i386/Kconfig.cpu +1
-0+ depends on !X86_VMIhelp
Select this for a 486 series processor, either Intel or one of the compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,arch/i386/Kconfig.cpu +0
-0@@ -55,6 +57,7 @@ config M486config M586
bool "586/K5/5x86/6x86/6x86MX"arch/i386/Kconfig.cpu +1
-0+ depends on !X86_VMIhelp
Select this for an 586 or 686 series processor such as the AMD K5, the Cyrix 5x86, 6x86 and 6x86MX. This choice does notarch/i386/Kconfig.cpu +0
-0@@ -62,12 +65,14 @@ config M586config M586TSC
bool "Pentium-Classic"arch/i386/Kconfig.cpu +1
-0+ depends on !X86_VMIhelp
Select this for a Pentium Classic processor with the RDTSC (Read Time Stamp Counter) instruction for benchmarking.config M586MMX
bool "Pentium-MMX"arch/i386/Kconfig.cpu +1
-0+ depends on !X86_VMIhelp
Select this for a Pentium with the MMX graphics/multimedia extended instructions.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines · Zachary Amsden
Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only are designed to run on modern hardware platforms. As such, they require a working APIC, and do not support some legacy functionality, including APM BIOS, ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of dropping ISA support). They also require a P6 series CPU.
That's pretty bad because distributors need another kernel still. At least a working APIC isn't quite as common today as it should.
Quoted 9 lines · Christoph Hellwig
Quoted 6 lines · Zachary Amsden
Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only are designed to run on modern hardware platforms. As such, they require a working APIC, and do not support some legacy functionality, including APM BIOS, ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of dropping ISA support). They also require a P6 series CPU.
Quoted 3 lines
That's pretty bad because distributors need another kernel still. At least a working APIC isn't quite as common today as it should.
It doesn't need to be a fully functional APIC. It just needs to not have one particular bug - Pentium processor erratum 11AP. There is no reason that most of these requirements can't be dropped. We used to have a lot more functionality and legacy support turned off, and we gradually turned it back on. Turning on the BIOS interfaces will cause complications for a VMI kernel running in a hypervisor - since it can't invoke non-virtualized BIOS code. So it does require a bit of conditional logic, which is pretty easy, but we haven't got around to doing yet.
Zach
Quoted 8 lines · Zachary Amsden
Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only are designed to run on modern hardware platforms. As such, they require a working APIC, and do not support some legacy functionality, including APM BIOS, ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of dropping ISA support). They also require a P6 series CPU.
Signed-off-by Zachary Amsden <[email protected]>
arch/i386/Kconfig config X86_ES7000 · line 153
Quoted 9 lines
arch/i386/Kconfig +9
-0+menu "VMI configurable support" + depends on X86_VMI + +config VMI_REQUIRE_HYPERVISOR + bool "Require hypervisor" + default n + help + This option forces the kernel to run with a hypervisor present. + The kernel will panic if booted on native hardware.
This uses spaces instead of tabs...
arch/i386/Kconfig config X86_VISWS_APIC · line 301
Quoted 9 lines
arch/i386/Kconfig +1
-1@@ -270,7 +295,7 @@ config X86_VISWS_APIC config X86_MCE bool "Machine Check Exception" - depends on !X86_VOYAGER + depends on !(X86_VOYAGER) ---help--- Machine Check Exception support allows the processor to notify the kernel if it detects a problem (e.g. overheating, component
And you probalby do not need this change.
arch/i386/Kconfig config X86_MCE_P4THERMAL · line 338
Quoted 8 lines
arch/i386/Kconfig +1
-0@@ -307,6 +332,7 @@ config X86_MCE_P4THERMAL config TOSHIBA tristate "Toshiba Laptop support" + depends on !X86_VMI ---help--- This adds a driver to safely access the System Management Mode of the CPU on Toshiba portables with a genuine Toshiba BIOS. It
In the long run, we'd like to support toshiba laptops :-)
Pavel
Signature · 1 line
135: uint Size;
Quoted 8 lines
Quoted 7 lines
Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only are designed to run on modern hardware platforms. As such, they require a working APIC, and do not support some legacy functionality, including APM BIOS, ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of dropping ISA support). They also require a P6 series CPU.
Maybe I'm mixing things, but if VMware is capable of running on a i586 (=P5?) (like AMD K6 - and it certainly is capable of doing that), should not VMI be similar?
For example, the TM5800 CPU which is somewhat of a mixture between i586 and i686 but does not have an IOAPIC can run VMware machines (although painfully slow).
And, the last thing, distributor kernels are often compiled for i586 to be generic to all users. But some users may actually run them on i686, and these users would like to have VMI (speculation :-). Which would include a forceful patch to Kconfig to have the VMI option available with CONFIG_M586.
Quoted 2 lines
That's pretty bad because distributors need another kernel still. At least a working APIC isn't quite as common today as it should.
Jan Engelhardt
Quoted 6 lines · Jan Engelhardt
And, the last thing, distributor kernels are often compiled for i586 to be generic to all users. But some users may actually run them on i686, and these users would like to have VMI (speculation :-). Which would include a forceful patch to
Kconfigto have the VMI option available withCONFIG_M586.
We can reenable all these things eventually. We hacked them out to get around some of the awful hacks required for these older machines, (F00F bug protection, broken APICs, etc).