[PATCH 0/5] QEMU VFIO live migration

[Gonglei (Arei)]

> -----Original Message-----
> From: Zhao Yan [mailto:yan.y.zhao at intel.com]
> Sent: Thursday, February 21, 2019 10:05 AM
> To: Gonglei (Arei) <arei.gonglei at huawei.com>
> Cc: alex.williamson at redhat.com; qemu-devel at nongnu.org;
> intel-gvt-dev at lists.freedesktop.org; Zhengxiao.zx at Alibaba-inc.com;
> yi.l.liu at intel.com; eskultet at redhat.com; ziye.yang at intel.com;
> cohuck at redhat.com; shuangtai.tst at alibaba-inc.com; dgilbert at redhat.com;
> zhi.a.wang at intel.com; mlevitsk at redhat.com; pasic at linux.ibm.com;
> aik at ozlabs.ru; eauger at redhat.com; felipe at nutanix.com;
> jonathan.davies at nutanix.com; changpeng.liu at intel.com; Ken.Xue at amd.com;
> kwankhede at nvidia.com; kevin.tian at intel.com; cjia at nvidia.com;
> kvm at vger.kernel.org
> Subject: Re: [PATCH 0/5] QEMU VFIO live migration
> 
> > >
> > > > 5) About log sync, why not register log_global_start/stop in
> > > vfio_memory_listener?
> > > >
> > > >
> > > seems log_global_start/stop cannot be iterately called in pre-copy phase?
> > > for dirty pages in system memory, it's better to transfer dirty data
> > > iteratively to reduce down time, right?
> > >
> >
> > We just need invoking only once for start and stop logging. Why we need to
> call
> > them literately? See memory_listener of vhost.
> >
> the dirty pages in system memory produces by device is incremental.
> if it can be got iteratively, the dirty pages in stop-and-copy phase can be
> minimal.
> :)
> 
I mean starting or stopping the capability of logging, not log sync. 

We register the below callbacks:

.log_sync = vfio_log_sync,
.log_global_start = vfio_log_global_start,
.log_global_stop = vfio_log_global_stop,

Regards,
-Gonglei