On Wed, Mar 25, 2020 at 04:52:52PM +0000, Dr. David Alan Gilbert wrote: > * Peter Xu (pet...@redhat.com) wrote: > > Some of the memory listener may want to do log synchronization without > > being able to specify a range of memory to sync but always globally. > > Such a memory listener should provide this new method instead of the > > log_sync() method. > > > > Obviously we can also achieve similar thing when we put the global > > sync logic into a log_sync() handler. However that's not efficient > > enough because otherwise memory_global_dirty_log_sync() may do the > > global sync N times, where N is the number of flat views. > > > > Make this new method be exclusive to log_sync(). > > > > Signed-off-by: Peter Xu <pet...@redhat.com> > > OK, so I guess the idea here is that when you have a ring with dirty > pages on it, you just need to clear all outstanding things on the ring > whereever they came from.
Yeah, or say it's about granularity of log_sync(), and the ring layout will only be able to sync in a global manner rather than per-memslot. It's actually not good when we only want to sync some specific small memory region (e.g., the VGA code wants to only sync the VGA ram), but we don't have much choice... > > Reviewed-by: Dr. David Alan Gilbert <dgilb...@redhat.com> Thanks! -- Peter Xu