From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Baffled by multipage_allocation_permitted() Date: Mon, 15 Jun 2009 22:57:03 +0100 Message-ID: References: <200906151644.51978.dcm@mccr.org> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200906151644.51978.dcm@mccr.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dave McCracken , Xen Developers List List-Id: xen-devel@lists.xenproject.org On 15/06/2009 22:44, "Dave McCracken" wrote: > #define multipage_allocation_permitted(d) \ > (!rangeset_is_empty((d)->iomem_caps) || \ > !rangeset_is_empty((d)->arch.ioport_caps)) > > I had never tracked down the significance of this macro since it didn't appear > to be an issue. Now it's suddenly denying me the ability to work in 2M pages. > > What is this macro trying to achieve? Why is it necessary? Is there any > compelling reason we can't just remove it and allow multipage allocations from > any domain? We can just get rid of it I think. There are arguably worse other things we already allow, like any guest can allocate low memory by specifying a small value of XENMEMF_address_bits(). -- Keir