[uml-devel] [PATCH] slight UML config simplification.

[Rob Landley <rob@landley.net>]

[-- Attachment #1: Type: text/plain, Size: 279 bytes --]

Since -tt mode is going to go the way of the dodo when -skas0 stabilizies (and 
-skas0 "works for me"), start making options that only affect -tt mode depend 
on -tt mode (and group them together).

Start with "nesting level".

Rob

Signed-off-by: Rob Landley <rob@landley.net>


[-- Attachment #2: thing.patch --]
[-- Type: text/x-diff, Size: 2003 bytes --]

--- linux-2.6.13.1/arch/um/Kconfig	2005-09-09 21:42:58.000000000 -0500
+++ linux-2.6.13.1-new/arch/um/Kconfig	2005-10-08 18:24:33.968546648 -0500
@@ -63,6 +63,23 @@
 	chroot, and you disable CONFIG_MODE_TT, you probably want to say Y
 	here.
 
+config NEST_LEVEL
+	int "Nesting level"
+	default "0"
+	depends on MODE_TT
+	help
+        This is set to the number of layers of UMLs that this UML will be run
+        in.  Normally, this is zero, meaning that it will run directly on the
+        host.  Setting it to one will build a UML that can run inside a UML
+        that is running on the host.  Generally, if you intend this UML to run
+        inside another UML, set CONFIG_NEST_LEVEL to one more than the host
+        UML.
+
+        Note that if the hosting UML has its CONFIG_KERNEL_HALF_GIGS set to
+        greater than one, then the guest UML should have its CONFIG_NEST_LEVEL
+        set to the host's CONFIG_NEST_LEVEL + CONFIG_KERNEL_HALF_GIGS.
+        Only change this if you are running nested UMLs.
+
 config MODE_SKAS
 	bool "Separate Kernel Address Space support"
 	default y
@@ -223,22 +240,6 @@
 	depends on SMP
 	default "32"
 
-config NEST_LEVEL
-	int "Nesting level"
-	default "0"
-	help
-        This is set to the number of layers of UMLs that this UML will be run
-        in.  Normally, this is zero, meaning that it will run directly on the
-        host.  Setting it to one will build a UML that can run inside a UML
-        that is running on the host.  Generally, if you intend this UML to run
-        inside another UML, set CONFIG_NEST_LEVEL to one more than the host
-        UML.
-
-        Note that if the hosting UML has its CONFIG_KERNEL_HALF_GIGS set to
-        greater than one, then the guest UML should have its CONFIG_NEST_LEVEL
-        set to the host's CONFIG_NEST_LEVEL + CONFIG_KERNEL_HALF_GIGS.
-        Only change this if you are running nested UMLs.
-
 config KERNEL_HALF_GIGS
 	int "Kernel address space size (in .5G units)"
 	default "1"