From: David Vrabel Subject: Re: [Patch V2 2/2] xen: before ballooning hotplugged memory, set frames to invalid Date: Mon, 23 Mar 2015 11:59:27 +0000 Message-ID: <5510001F.7020706@citrix.com> References: <1426856139-3359-1-git-send-email-jgross@suse.com> <1426856139-3359-3-git-send-email-jgross@suse.com> <20150320134642.GJ27971@olila.local.net-space.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150320134642.GJ27971@olila.local.net-space.pl> Sender: linux-kernel-owner@vger.kernel.org To: Daniel Kiper , Juergen Gross Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, konrad.wilk@oracle.com, boris.ostrovsky@oracle.com, pebolle@tiscali.nl List-Id: xen-devel@lists.xenproject.org On 20/03/15 13:46, Daniel Kiper wrote: > On Fri, Mar 20, 2015 at 01:55:39PM +0100, Juergen Gross wrote: >> Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set >> regions above the end of RAM as 1:1") introduced a regression. >> > > Should not we fill everything above "maxmem" with > INVALID_P2M_ENTRY at boot time? No. See the commit referenced above. David