[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC PATCH] xen/arm: Vmap allocator fails to allocate beyond 128M



>>> On 24.02.15 at 11:20, <ian.campbell@xxxxxxxxxx> wrote:
> On Tue, 2015-02-24 at 10:01 +0000, Jan Beulich wrote:
>> >>> On 23.02.15 at 18:03, <ian.campbell@xxxxxxxxxx> 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.

Fine with me.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.