Re: [Xen-devel] [PATCH XEN v5 14/23] tools: foreignmemory: provide xenforeignmemory_unmap.

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Wed, 2015-11-11 at 15:14 +0000, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH XEN v5 14/23] tools: foreignmemory: provide
> xenforeignmemory_unmap."):
> > And require it be used instead of direct munmap.
> > 
> > This will allow e.g. Valgrind hooks to help track incorrect use of
> > foreign mappings.
> > 
> > Switch all uses of xenforeignmemory_map to use
> > xenforeignmemory_unmap, not that foreign mappings via the libxc compat
> > xc_map_foreign_* interface will not take advantage of this and will
> > need converting.
> ...
> > +int xenforeignmemory_unmap(xenforeignmemory_handle *fmem,
> > +ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂvoid *addr, unsigned int num);
> > +
> 
> What kind of errors might this return ?

Same as munmap(2), i.e. only EINVAL according toÂhttp://pubs.opengroup.org/
onlinepubs/9699919799/functions/munmap.html

Ian,

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