|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] Block I/O outside the QEMU global mutex was "Re: [RFC PATCH 00/17] Support for multiple "AIO contexts"" |
Date: | Tue, 09 Oct 2012 16:41:22 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 |
On 10/09/2012 04:35 PM, Paolo Bonzini wrote: >> Of course we can violate that and it wouldn't know a thing, but I prefer >> to stick to the established pattern. > > I wasn't suggesting that, just evaluating the different tradeoffs QEMU > could make. Reference counting is complicated because it has to apply > to all objects used as opaques, and we're using things other than the > DeviceState as opaques in many cases. In the last episode we had MemoryRegionOps::ref/unref() to work around that. But yes, it's complicated, and we haven't started to deal with cycles yet. -- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |