On 04/04/2017 12:23, Gerd Hoffmann wrote: > > memory_region_copy_and_clear_dirty() will create a copy of the dirty > bitmap for the specified range, clear the dirty bitmap and return the > copy. The returned bitmap can be a bit larger than requested, the range > is expanded so the code can copy unsigned longs from the bitmap and > avoid atomic bit update operations. > > memory_region_copy_get_dirty() will return the dirty status of pages, > pretty much like memory_region_get_dirty(), but using the copy returned > by memory_region_copy_and_clear_dirty().
Old names in the commit message, otherwise looks good. This will also help KVM by the way, because there are changes in the pipeline to limit the amount of work done by log_sync and process dirty pages periodically in the VCPU thread. Paolo