search for: balloon_alloc_empty_page_range

When I read the blkfront.c and blkback.c, I noticed that in some places (e.g, map_frontend_page()) it uses alloc_vm_area() to allocate memory for foreign page mapping. However, in some other places, it used balloon_alloc_empty_page_range() to allocate memory for mapping. What''s the difference between these two functions? Why not just use one function like alloc_vm_area() or balloon_alloc_empty_page_range()? More important, I noticed that with alloc_vm_area(), it requires lock_vm_area() to lock down the vm area. Why do we...

...d seems overly harsh (we''re having a case where this actually happens); wouldn''t it make sense to make this fatal only when the page can''t be replaced by a free one (allocated inside the domain, with the page stolen for this then simply pushed into the balloon, similar to balloon_alloc_empty_page_range() except without freeing the memory to Xen)? Thanks for clarification, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel