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
