[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 11/15] lock: introduce global lock for device tr
From: |
liu ping fan |
Subject: |
Re: [Qemu-devel] [PATCH 11/15] lock: introduce global lock for device tree |
Date: |
Thu, 9 Aug 2012 15:27:59 +0800 |
On Wed, Aug 8, 2012 at 5:42 PM, Avi Kivity <address@hidden> wrote:
> On 08/08/2012 09:25 AM, Liu Ping Fan wrote:
>> From: Liu Ping Fan <address@hidden>
>>
>
> Please explain the motivation. AFAICT, the big qemu lock is sufficient.
>
Oh, this is one of the series locks for the removal of big qemu lock.
The degradation of big lock will take several steps, including to
introduce device's private lock. Till then, when the device add path
from iothread and the remove path in io-dispatch is out of the big
qemu lock. We need this extra lock.
These series is too big, so I send out the 1st phase for review.
Regards,
pingan
>
> --
> error compiling committee.c: too many arguments to function
- [Qemu-devel] [PATCH 15/15] e1000: using new interface--unmap to unplug, (continued)
[Qemu-devel] [PATCH 11/15] lock: introduce global lock for device tree, Liu Ping Fan, 2012/08/08
Re: [Qemu-devel] [PATCH 11/15] lock: introduce global lock for device tree, Avi Kivity, 2012/08/08
[Qemu-devel] [PATCH 12/15] qdev: using devtree lock to protect device's accessing, Liu Ping Fan, 2012/08/08
[Qemu-devel] [PATCH 07/15] memory: inc/dec mr's ref when adding/removing from mem view, Liu Ping Fan, 2012/08/08
[Qemu-devel] [PATCH 14/15] qom: object_unref call reclaimer, Liu Ping Fan, 2012/08/08
[Qemu-devel] [PATCH 08/15] memory: introduce PhysMap to present snapshot of toploygy, Liu Ping Fan, 2012/08/08