> On 25 May 2017, at 01:36, Peter Xu wrote:
>
> On Wed, May 24, 2017 at 01:02:25PM +, Felipe Franciosi wrote:
>>
>>> On 23 May 2017, at 05:27, Peter Xu wrote:
>>>
>>> On Fri, May 19, 2017 at 10:59:02PM +0100, Felipe Franciosi wrote:
The first time migration_bitmap_sync() is called, b
On Wed, May 24, 2017 at 01:02:25PM +, Felipe Franciosi wrote:
>
> > On 23 May 2017, at 05:27, Peter Xu wrote:
> >
> > On Fri, May 19, 2017 at 10:59:02PM +0100, Felipe Franciosi wrote:
> >> The first time migration_bitmap_sync() is called, bytes_xfer_prev is set
> >> to ram_state.bytes_transf
> On 23 May 2017, at 05:27, Peter Xu wrote:
>
> On Fri, May 19, 2017 at 10:59:02PM +0100, Felipe Franciosi wrote:
>> The first time migration_bitmap_sync() is called, bytes_xfer_prev is set
>> to ram_state.bytes_transferred which is, at this point, zero. The next
>> time migration_bitmap_sync()
On Fri, May 19, 2017 at 10:59:02PM +0100, Felipe Franciosi wrote:
> The first time migration_bitmap_sync() is called, bytes_xfer_prev is set
> to ram_state.bytes_transferred which is, at this point, zero. The next
> time migration_bitmap_sync() is called, an iteration has happened and
> bytes_xfer_
The first time migration_bitmap_sync() is called, bytes_xfer_prev is set
to ram_state.bytes_transferred which is, at this point, zero. The next
time migration_bitmap_sync() is called, an iteration has happened and
bytes_xfer_prev is set to 'x' bytes. Most likely, more than one second
has passed, so