Commit fe33f6f1 authored by Jeff Dike's avatar Jeff Dike Committed by Linus Torvalds

[PATCH] Fix UML on non-standard VM split hosts

This fixes UML on hosts with non-standard VM splits.  We had changed the
config variable that controls UML behavior on such hosts, but not
propogated the change everywhere.  In particular, the values of STUB_CODE
and STUB_DATA relied on the old variable.

I also reformatted the HOST_VMSPLIT_3G help to make it more standard.

Spotted by uml@flonatel.org.
Signed-off-by: default avatarJeff Dike <jdike@addtoit.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>
Cc: Pravin <shindepravin@gmail.com>
Cc: <uml@flonatel.org>
Cc: <stable@kernel.org>
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 569d3287
...@@ -19,7 +19,7 @@ config SEMAPHORE_SLEEPERS ...@@ -19,7 +19,7 @@ config SEMAPHORE_SLEEPERS
choice choice
prompt "Host memory split" prompt "Host memory split"
default HOST_VMSPLIT_3G default HOST_VMSPLIT_3G
---help--- help
This is needed when the host kernel on which you run has a non-default This is needed when the host kernel on which you run has a non-default
(like 2G/2G) memory split, instead of the customary 3G/1G. If you did (like 2G/2G) memory split, instead of the customary 3G/1G. If you did
not recompile your own kernel but use the default distro's one, you can not recompile your own kernel but use the default distro's one, you can
...@@ -67,13 +67,13 @@ config 3_LEVEL_PGTABLES ...@@ -67,13 +67,13 @@ config 3_LEVEL_PGTABLES
config STUB_CODE config STUB_CODE
hex hex
default 0xbfffe000 if !HOST_2G_2G default 0xbfffe000 if !HOST_VMSPLIT_2G
default 0x7fffe000 if HOST_2G_2G default 0x7fffe000 if HOST_VMSPLIT_2G
config STUB_DATA config STUB_DATA
hex hex
default 0xbffff000 if !HOST_2G_2G default 0xbffff000 if !HOST_VMSPLIT_2G
default 0x7ffff000 if HOST_2G_2G default 0x7ffff000 if HOST_VMSPLIT_2G
config STUB_START config STUB_START
hex hex
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment