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

Re: [Xen-devel] [PATCH v3 1/5] move XENMEM_add_to_physmap handling framework to common code



On Fri, 2013-12-20 at 10:41 +0000, Jan Beulich wrote:
> There's really nothing really architecture specific here; the
> architecture specific handling is limited to
> xenmem_add_to_physmap_one().
> 
> 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>
(nb: I didn't look at the x86 bits at all...)

> ---
> v3: Restriction of XENMAPSPACE_gmfn_foreign only being possible via
>     XENMEM_add_to_physmap_range no longer being dropped.

Thanks.

Ian.


_______________________________________________
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®.