Re: [Xen-devel] [PATCH] xenmem_add_to_physmap_one() has no need to know of XENMAPSPACE_gmfn_range

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 06/12/17 16:21, Jan Beulich wrote:
> As its name says, it handles a single GMFN only anyway. Note that ARM
> needs no adjustment, as it doesn't handle the two types at all.
>
> Also take the opportunity and clean up the handling of XENMAPSPACE_gmfn
> a little: There's no point in going through "idx" when capturing the MFN.
>
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

This looks to be based on some of your other mm cleanup, which isn't yet
in staging.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel