* alloc_vm_area() calling vmalloc_sync_all()
@ 2007-11-19 9:39 Jan Beulich
2007-11-19 11:52 ` Keir Fraser
0 siblings, 1 reply; 2+ messages in thread
From: Jan Beulich @ 2007-11-19 9:39 UTC (permalink / raw)
To: xen-devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: alloc_vm_area() calling vmalloc_sync_all()
2007-11-19 9:39 alloc_vm_area() calling vmalloc_sync_all() Jan Beulich
@ 2007-11-19 11:52 ` Keir Fraser
0 siblings, 0 replies; 2+ messages in thread
From: Keir Fraser @ 2007-11-19 11:52 UTC (permalink / raw)
To: Jan Beulich, xen-devel
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@novell.com> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-19 11:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-19 9:39 alloc_vm_area() calling vmalloc_sync_all() Jan Beulich
2007-11-19 11:52 ` Keir Fraser
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.