On 11/29/18 12:07 PM, Jan Beulich wrote: >>>> On 28.11.18 at 22:56, <rcojoc...@bitdefender.com> wrote: >> change_range_type() 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> >> >> --- >> CC: George Dunlap <george.dun...@eu.citrix.com> >> CC: Jan Beulich <jbeul...@suse.com> >> CC: Andrew Cooper <andrew.coop...@citrix.com> >> CC: Wei Liu <wei.l...@citrix.com> >> CC: "Roger Pau Monné" <roger....@citrix.com> >> >> --- >> Changes since V9: >> - Corrected function name in patch subject. > > Funny: I didn't even notice the issue in the patch title. I had > pointed it out against the start of the description, where it > still exists.
Right, I'll correct that as well. Thanks, Razvan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
