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

Re: [Xen-devel] [PATCH v3 4/5] fix XENMEM_add_to_physmap_range preemption handling



On Fri, 2013-12-20 at 10:43 +0000, Jan Beulich wrote:
> Just like for all other hypercalls we shouldn't be modifying the input
> structure - all of the fields are, even if not explicitly documented,
> just inputs (the one OUT one really refers to the memory pointed to by
> that handle rather than the handle itself).
> 
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
> Reviewed-by: Tim Deegan <tim@xxxxxxx>
> Acked-by: Keir Fraser <keir@xxxxxxx>

Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>



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


 


Rackspace

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