Re: [Qemu-devel] [PATCH] migration: keep bytes_xfer_prev init'd to zero

2017-05-25 Thread Felipe Franciosi
> 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

Re: [Qemu-devel] [PATCH] migration: keep bytes_xfer_prev init'd to zero

2017-05-24 Thread Peter Xu
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

Re: [Qemu-devel] [PATCH] migration: keep bytes_xfer_prev init'd to zero

2017-05-24 Thread Felipe Franciosi
> 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

Re: [Qemu-devel] [PATCH] migration: keep bytes_xfer_prev init'd to zero

2017-05-22 Thread Peter Xu
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 >

[Qemu-devel] [PATCH] migration: keep bytes_xfer_prev init'd to zero

2017-05-19 Thread Felipe Franciosi
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,