On 12/5/18 9:18 AM, Razvan Cojocaru wrote: > change_type_range() invalidates gfn ranges to lazily change the type > of a range of gfns, and also modifies the logdirty rangesets of that > p2m. At the moment, it clips both down by the hostp2m. > > While this will result in correct behavior, it's not entirely efficient, > since invalidated entries outside that range will, on fault, simply be > modified back to "empty" before faulting normally again. > > Separate out the calculation of the two ranges. Keep using the > hostp2m's max_mapped_pfn to clip the logdirty ranges, but use the > current p2m's max_mapped_pfn to further clip the invalidation range > for alternate p2ms. > > Signed-off-by: George Dunlap <george.dun...@citrix.com> > Signed-off-by: Razvan Cojocaru <rcojoc...@bitdefender.com> > Reviewed-by: Jan Beulich <jbeul...@suse.com> > Tested-by: Tamas K Lengyel <ta...@tklengyel.com>
Acked-by: George Dunlap <george.dun...@citrix.com> So it looks like as soon as we get patch 4 into shape we can check this in. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel