From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 2/2] x86/xen: during early setup, only 1:1 map the ISA region Date: Fri, 16 Aug 2013 16:39:06 +0100 Message-ID: <520E479A.9010004@citrix.com> References: <1376664176-27535-1-git-send-email-david.vrabel@citrix.com> <1376664176-27535-3-git-send-email-david.vrabel@citrix.com> <20130816152553.GD12047@konrad-lan.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130816152553.GD12047@konrad-lan.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Boris Ostrovsky , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 16/08/13 16:25, Konrad Rzeszutek Wilk wrote: > On Fri, Aug 16, 2013 at 03:42:56PM +0100, David Vrabel wrote: >> From: David Vrabel >> >> During early setup, when the reserved regions and MMIO holes are being >> setup as 1:1 in the p2m, clear any mappings instead of making them 1:1 >> (execept for the ISA region which is expected to be mapped). >> >> This reverts a change in behaviour introduced in 3.5 by 83d51ab473dd >> (xen/setup: update VA mapping when releasing memory during setup). > > So it won't cause the original issues to reappear which is that we > get this > > (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 2097153 > 2097152 > (XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 17) > > if we boot without dom0_mem_max ? No, because the mapping is either updated or cleared. David