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

2015-02-17 Thread Julien Grall
Hello Vijay, The title looks more a title for a bug report rather than a patch. On 17/02/15 06:07, Vijay Kilari wrote: > In vmap_init, map_pages_to_xen() is called for mapping > vm_bitmap. Initially one page of vm_bitmap is allocated > and mapped using PAGE_HYPERVISOR attribute. > For the rest of

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

2015-02-17 Thread Jan Beulich
>>> On 17.02.15 at 07:07, wrote: > In vmap_init, map_pages_to_xen() is called for mapping > vm_bitmap. Initially one page of vm_bitmap is allocated > and mapped using PAGE_HYPERVISOR attribute. > For the rest of vm_bitmap pages, MAP_SMALL_PAGES attribute > is used to map. > > In ARM for both PAGE

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

2015-02-16 Thread Vijay Kilari
In vmap_init, map_pages_to_xen() is called for mapping vm_bitmap. Initially one page of vm_bitmap is allocated and mapped using PAGE_HYPERVISOR attribute. For the rest of vm_bitmap pages, MAP_SMALL_PAGES attribute is used to map. In ARM for both PAGE_HYPERVISOR and MAP_SMALL_PAGES, valid bit is se