From: David Vrabel Subject: Re: [Xen-devel] [PATCH V2 1/5] Xen: Delay remapping memory of pv-domain Date: Fri, 7 Nov 2014 14:57:58 +0000 Message-ID: <545CDDF6.9080902@citrix.com> References: <1415252853-7106-1-git-send-email-jgross@suse.com> <1415252853-7106-2-git-send-email-jgross@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1415252853-7106-2-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, x86@kernel.org, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com List-Id: xen-devel@lists.xenproject.org On 06/11/14 05:47, Juergen Gross wrote: > Early in the boot process the memory layout of a pv-domain is changed > to match the E820 map (either the host one for Dom0 or the Xen one) > regarding placement of RAM and PCI holes. This requires removing memory > pages initially located at positions not suitable for RAM and adding > them later at higher addresses where no restrictions apply. > > To be able to operate on the hypervisor supported p2m list until a > virtual mapped linear p2m list can be constructed, remapping must > be delayed until virtual memory management is initialized, as the > initial p2m list can't be extended unlimited at physical memory > initialization time due to it's fixed structure. > > A further advantage is the reduction in complexity and code volume as > we don't have to be careful regarding memory restrictions during p2m > updates. Reviewed-by: David Vrabel But I would like a second reviewed-by. David