Am 08.03.2018 um 10:01 schrieb Fam Zheng:
On Thu, Mar 8, 2018 at 4:57 PM, Peter Lieven wrote:
Am 08.03.2018 um 02:28 schrieb Fam Zheng :
On Wed, 03/07 09:06, Peter Lieven wrote:
Hi,
while looking at the code I wonder if the blk_aio_preadv and the
bdrv_reset_dirty_bitmap order must
be swap
On Thu, Mar 8, 2018 at 4:57 PM, Peter Lieven wrote:
>
>
>> Am 08.03.2018 um 02:28 schrieb Fam Zheng :
>>
>>> On Wed, 03/07 09:06, Peter Lieven wrote:
>>> Hi,
>>>
>>> while looking at the code I wonder if the blk_aio_preadv and the
>>> bdrv_reset_dirty_bitmap order must
>>> be swapped in mig_save_
> Am 08.03.2018 um 02:28 schrieb Fam Zheng :
>
>> On Wed, 03/07 09:06, Peter Lieven wrote:
>> Hi,
>>
>> while looking at the code I wonder if the blk_aio_preadv and the
>> bdrv_reset_dirty_bitmap order must
>> be swapped in mig_save_device_bulk:
>>
>>qemu_mutex_lock_iothread();
>>aio_
On Wed, 03/07 09:06, Peter Lieven wrote:
> Hi,
>
> while looking at the code I wonder if the blk_aio_preadv and the
> bdrv_reset_dirty_bitmap order must
> be swapped in mig_save_device_bulk:
>
> qemu_mutex_lock_iothread();
> aio_context_acquire(blk_get_aio_context(bmds->blk));
> blk-
Hi,
while looking at the code I wonder if the blk_aio_preadv and the
bdrv_reset_dirty_bitmap order must
be swapped in mig_save_device_bulk:
qemu_mutex_lock_iothread();
aio_context_acquire(blk_get_aio_context(bmds->blk));
blk->aiocb = blk_aio_preadv(bb, cur_sector * BDRV_SECTOR_SIZE,