From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [RFC PATCH] xen/arm: Vmap allocator fails to allocate beyond 128M Date: Tue, 24 Feb 2015 10:20:49 +0000 Message-ID: <1424773249.27930.295.camel@citrix.com> References: <1424710994.27930.226.camel@citrix.com> <54EC59F80200007800062FA9@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54EC59F80200007800062FA9@mail.emea.novell.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: Jan Beulich Cc: Vijay Kilari , Stefano Stabellini , Julien Grall , Tim Deegan , "xen-devel@lists.xen.org" , StefanoStabellini List-Id: xen-devel@lists.xenproject.org On Tue, 2015-02-24 at 10:01 +0000, Jan Beulich wrote: > >>> On 23.02.15 at 18:03, wrote: > > Can we along with this fix perhaps rename to something which does > > indicate this. MAP_NON_LEAF_PTS or something perhaps? (This is really a > > question for Jan). > > Renaming wouldn't be the right thing - we'd need a second flag. > Indeed I've been (ab)using behavior of the x86 implementation > here that's neither documented nor necessarily obvious. How about a new arch interface like create_mapping_pts or populate_pt_range or some such which provides the semantics you want? On x86 it could just be implemented using map_pages_to_xen(..., MAP_SMALL_PAGES) and on ARM we'd figure it out somehow. Ian.