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

Re: [Xen-devel] alloc_vm_area() calling vmalloc_sync_all()


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Mon, 19 Nov 2007 11:52:43 +0000
  • Delivery-date: Mon, 19 Nov 2007 03:53:35 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgqorFv7/hTbpaVEdyzdgAX8io7RQ==
  • Thread-topic: [Xen-devel] alloc_vm_area() calling vmalloc_sync_all()

Yes, the virtual address returned gets passed to e.g.,
GNTTABOP_map_grant_ref, so the area must be mapped in the current address
space immediately. It can't be demand faulted.

 -- Keir


On 19/11/07 09:39, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Is there a specific reason for this? Other VM area functions don't do this
> pro-actively, and native only needs this for allowing NMI and MCE notifiers
> access to vmalloc space (which is being taken care of when registering
> such handlers).
> 
> Thanks, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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