From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [Xen-devel] [PATCH] xen: limit memory to architectural maximum Date: Fri, 4 Sep 2015 16:43:45 +0100 Message-ID: <55E9BC31.6000502@citrix.com> References: <1441369088-11680-1-git-send-email-jgross@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1441369088-11680-1-git-send-email-jgross@suse.com> Sender: linux-kernel-owner@vger.kernel.org To: Juergen Gross , linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, konrad.wilk@oracle.com, david.vrabel@citrix.com, boris.ostrovsky@oracle.com List-Id: xen-devel@lists.xenproject.org On 04/09/15 13:18, Juergen Gross wrote: > When a pv-domain (including dom0) is started it tries to size it's > p2m list according to the maximum possible memory amount it ever can > achieve. Limit the initial maximum memory size to the architectural > limit of the hardware in order to avoid overflows during remapping > of memory. > > This problem will occur when dom0 is started with an initial memory > size being a multiple of 1GB, but without specifying it's maximum > memory size. The kernel must be configured without > CONFIG_XEN_BALLOON_MEMORY_HOTPLUG for the problem to happen. Applied to for-linus-4.3, thanks. David