Hi,
On Sun, Aug 26, 2012 at 10:51:29AM -0500, Anthony Liguori wrote:
> Right now, you need to pair up object_new with object_delete. This is
> impractical when using reference counting because we would like to ensure that
> object_unref() also frees memory when needed.
>
> The first few patches
Paolo Bonzini writes:
> Il 27/08/2012 13:46, Andreas Färber ha scritto:
>>
>> Since link and child properties all hold references, in order to
>> actually free
>> an object, we need to break those links. User created devices end up as
>> children of a container. But ch
Il 27/08/2012 13:46, Andreas Färber ha scritto:
>>> >>
>>> >> Since link and child properties all hold references, in order to
>>> >> actually free
>>> >> an object, we need to break those links. User created devices end up as
>>> >> children of a container. But child properties cannot be remove
Am 27.08.2012 09:22, schrieb liu ping fan:
> On Sun, Aug 26, 2012 at 11:51 PM, Anthony Liguori wrote:
>> Right now, you need to pair up object_new with object_delete. This is
>> impractical when using reference counting because we would like to ensure
>> that
>> object_unref() also frees memory
On Sun, Aug 26, 2012 at 11:51 PM, Anthony Liguori wrote:
> Right now, you need to pair up object_new with object_delete. This is
> impractical when using reference counting because we would like to ensure that
> object_unref() also frees memory when needed.
>
> The first few patches fix this prob
Right now, you need to pair up object_new with object_delete. This is
impractical when using reference counting because we would like to ensure that
object_unref() also frees memory when needed.
The first few patches fix this problem by introducing a release callback so
that objects that need spe
