Messages in this thread Patch in this message | | | From | Maxim Uvarov <> | Subject | [PATCH 2/2] xen: Make XEN_MAX_DOMAIN_MEMORY have more sensible defaults for 32-bit builds | Date | Fri, 14 Oct 2011 15:36:51 -0700 |
| |
Which is that 128GB is not going to happen with 32-bit PV DomU. Lets use something more realistic.
Signed-off-by: Maxim Uvarov <maxim.uvarov@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> --- arch/x86/xen/Kconfig | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig index 0b452c7..6d90ac8 100644 --- a/arch/x86/xen/Kconfig +++ b/arch/x86/xen/Kconfig @@ -29,7 +29,8 @@ config XEN_PVHVM config XEN_MAX_DOMAIN_MEMORY int "Maximum allowed size of a domain in gigabytes" - default 128 + default 128 if X86_64 + default 64 if X86_32 depends on XEN help This only affects the sizing of some bss arrays, the unused -- 1.7.4.1
| |