[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 1/8] block-migration: acquire AioContext as nece
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH 1/8] block-migration: acquire AioContext as necessary |
Date: |
Fri, 19 Feb 2016 16:02:50 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 |
On 16/02/2016 08:17, Fam Zheng wrote:
>> @@ -321,8 +339,9 @@ static int set_dirty_tracking(void)
>> int ret;
>>
>> QSIMPLEQ_FOREACH(bmds, &block_mig_state.bmds_list, entry) {
>> + /* Creating/dropping dirty bitmaps only requires the big QEMU lock.
>> */
>
> Why? I don't think it is safe today. The BDS state is mutated and it can race
> with bdrv_set_dirty() etc.
You're completely right.
> (Also the refresh_total_sectors in bdrv_nb_sectors
> can even do read/write, no?)
refresh_total_sectors will just do a lseek(SEEK_END) basically. So
that's safe.
Paolo
[Qemu-devel] [PATCH 2/8] vring: make vring_enable_notification return void, Paolo Bonzini, 2016/02/14
[Qemu-devel] [PATCH 3/8] virtio: add AioContext-specific function for host notifiers, Paolo Bonzini, 2016/02/14