Commit 80df4649 authored by Maxim Uvarov's avatar Maxim Uvarov Committed by Konrad Rzeszutek Wilk

xen: Make XEN_MAX_DOMAIN_MEMORY have more sensible defaults

Which is that 128GB is not going to happen with 32-bit PV DomU.
Lets use something more realistic. Also update the 64-bit to 500GB
which is the max a PV guest can do.
Signed-off-by: default avatarMaxim Uvarov <maxim.uvarov@oracle.com>
[v1: Updated 128GB->500GB for 64-bit]
Signed-off-by: default avatarKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
parent 92931abf
...@@ -29,7 +29,8 @@ config XEN_PVHVM ...@@ -29,7 +29,8 @@ config XEN_PVHVM
config XEN_MAX_DOMAIN_MEMORY config XEN_MAX_DOMAIN_MEMORY
int int
default 128 default 500 if X86_64
default 64 if X86_32
depends on XEN depends on XEN
help help
This only affects the sizing of some bss arrays, the unused This only affects the sizing of some bss arrays, the unused
...@@ -48,3 +49,4 @@ config XEN_DEBUG_FS ...@@ -48,3 +49,4 @@ config XEN_DEBUG_FS
help help
Enable statistics output and various tuning options in debugfs. Enable statistics output and various tuning options in debugfs.
Enabling this option may incur a significant performance overhead. Enabling this option may incur a significant performance overhead.
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