From: Maxim Uvarov <maxim.uvarov@oracle.com>
To: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
konrad.wilk@oracle.com, jeremy@goop.org
Cc: Maxim Uvarov <maxim.uvarov@oracle.com>
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 [thread overview]
Message-ID: <1318631811-21559-3-git-send-email-maxim.uvarov@oracle.com> (raw)
In-Reply-To: <1318631811-21559-1-git-send-email-maxim.uvarov@oracle.com>
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
next prev parent reply other threads:[~2011-10-14 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 22:36 [PATCH] XEN_DOMAIN_MEMORY options Maxim Uvarov
2011-10-14 22:36 ` [PATCH 1/2] xen: Fix XEN_MAX_DOMAIN_MEMORY to be selectable Maxim Uvarov
2011-10-14 22:36 ` Maxim Uvarov [this message]
2011-10-14 23:00 ` [PATCH] XEN_DOMAIN_MEMORY options Jeremy Fitzhardinge
2011-10-14 23:33 ` Maxim Uvarov
2011-10-14 23:41 ` Jeremy Fitzhardinge
2011-10-15 0:43 ` Maxim Uvarov
2011-10-15 13:05 ` Konrad Rzeszutek Wilk
2011-10-15 16:42 ` Ian Campbell
2011-10-19 14:05 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-10-19 14:04 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1318631811-21559-3-git-send-email-maxim.uvarov@oracle.com \
--to=maxim.uvarov@oracle.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).