qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v7 0/7] push mmio dispatch out of big lock


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH v7 0/7] push mmio dispatch out of big lock
Date: Mon, 06 May 2013 12:58:56 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4

Il 06/05/2013 12:56, Jan Kiszka ha scritto:
>> The problem is that even if I/O for a region is supposed to happen
>> within the BQL, lookup can happen outside the BQL.  Lookup will use the
>> region even if it is just to discard it:
>>
>>            VCPU thread (under BQL)              device thread
>>  
>> --------------------------------------------------------------------------------------
>>                                                 flatview_ref
>>                                                 memory_region_find returns 
>> d->mr
>>                                                 memory_region_ref(d->mr) /* 
>> nop */
>>            qdev_free(d)
>>              object_unparent(d)
>>                unrealize(d)
>>                  memory_region_del_subregion(d->mr)
>>                    FlatView updated, d->mr not in the new view
>>
>>                                                 flatview_unref
>>                                                   memory_region_unref(d->mr)
>>                                                     object_unref(d)
>>                                                       free(d)
>>                                                 if (!d->mr->is_ram) {        
>> /* BAD! */
>>                                                   memory_region_unref(d->mr) 
>> /* nop */
>>                                                   return error
>>                                                 }
>>
>>
>> Here, the memory region is dereferenced *before* we know that it is BQL-free
>> (in fact, exactly to ascertain whether it is BQL-free).
> 
> Both flatview update and lookup *plus* locking type evaluation (i.e.
> memory region dereferencing) always happen under the address space lock.
> See Pingfan's patch.

That's true of address_space_rw/map, but I don't think it holds for
memory_region_find.

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]