From: Paul Bolle <pebolle@tiscali.nl>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, david.vrabel@citrix.com,
boris.ostrovsky@oracle.com, daniel.kiper@oracle.com
Subject: Re: [PATCH 1/2] xen: prepare p2m list for memory hotplug
Date: Thu, 19 Mar 2015 20:15:05 +0100 [thread overview]
Message-ID: <1426792505.23529.10.camel@x220> (raw)
In-Reply-To: <1426775462-981-2-git-send-email-jgross@suse.com>
On Thu, 2015-03-19 at 15:31 +0100, Juergen Gross wrote:
> --- a/arch/x86/xen/p2m.c
> +++ b/arch/x86/xen/p2m.c
> +#ifdef CONFIG_X86_32
> +BUILD_BUG_ON_MSG(CONFIG_XEN_BALLOON_MEMORY_HOTPLUG_LIMIT > 64)
> +#endif
I assume BUILD_BUG_ON_MSG() aborts the build.
> --- a/drivers/xen/Kconfig
> +++ b/drivers/xen/Kconfig
> +config XEN_BALLOON_MEMORY_HOTPLUG_LIMIT
> + int
> + default 512 if X86_64
> + default 4 if X86_32
> + depends on XEN_HAVE_PVMMU
> + depends on XEN_BALLOON_MEMORY_HOTPLUG
> + help
> + Upper limit in GBs a pv domain can be expanded to using memory
> + hotplug.
> +
> + This value is used to allocate enough space in internal tables needed
> + for physical memory administration.
> +
I think adding a
range 1 64 if X86_32
would allow to drop the BUILD_BUG_ON_MSG(). (I haven't tested this so
you're allowed to bark at me if this ends up wasting your time.)
Paul Bolle
next prev parent reply other threads:[~2015-03-19 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 14:31 [PATCH 0/2] xen: fix regressions regarding memory hotplug in pv domains Juergen Gross
2015-03-19 14:31 ` [PATCH 1/2] xen: prepare p2m list for memory hotplug Juergen Gross
2015-03-19 15:53 ` Boris Ostrovsky
2015-03-19 17:01 ` Juergen Gross
2015-03-19 16:14 ` Daniel Kiper
2015-03-19 17:05 ` Juergen Gross
2015-03-19 16:18 ` [Xen-devel] " David Vrabel
2015-03-19 17:16 ` Juergen Gross
2015-03-19 17:22 ` David Vrabel
2015-03-19 19:15 ` Paul Bolle [this message]
2015-03-19 14:31 ` [PATCH 2/2] xen: before ballooning hotplugged memory, set frames to invalid Juergen Gross
2015-03-19 16:18 ` [Xen-devel] " David Vrabel
2015-03-19 17:19 ` Juergen Gross
2015-03-19 17:40 ` David Vrabel
2015-03-19 16:21 ` Daniel Kiper
2015-03-19 17:22 ` Juergen Gross
2015-03-19 18:40 ` Daniel Kiper
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=1426792505.23529.10.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--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