From: Anthony Liguori <anthony@codemonkey.ws>
To: alexander_barabash@mentor.com
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qom: Make object_unref() free the object's memory when refcount goes to 0.
Date: Wed, 22 Feb 2012 13:12:26 -0600 [thread overview]
Message-ID: <4F453E1A.9030701@codemonkey.ws> (raw)
In-Reply-To: <1329933650-30419-1-git-send-email-alexander_barabash@mentor.com>
On 02/22/2012 12:00 PM, alexander_barabash@mentor.com wrote:
> From: Alexander Barabash<alexander_barabash@mentor.com>
>
> In the existing implementation, object_delete()
> calls object_unref(), then frees the object's storage.
> Running object_delete() on an object with reference count
> different from 1 causes program failure.
>
> In the existing implementation, object_unref()
> finalizes the object when its reference count becomes 0.
>
> In the new implementation, object_unref()
> finalizes and frees the object's storage when the reference count becomes 0.
>
> In the new implementation, object_delete()
> just calls object_unref().
> Running object_delete() on an object with reference count
> different from 1 still causes program failure.
This isn't correct. QOM objects don't necessarily have heap allocated objects.
I've been thinking about this general problem and I think the right way to solve
it is to have a delete notifier list. That way, object_new() can register a
delete notifier that calls g_free() whenever refcount=0. That way an explicit
object_delete() isn't needed anymore.
Although I think we should keep the call around as it's convenient for replacing
occurrences of qdev_free() where you really want the assert.
Regards,
Anthony Liguori
>
> Signed-off-by: Alexander Barabash<alexander_barabash@mentor.com>
> ---
> qom/object.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/qom/object.c b/qom/object.c
> index e6591e1..8d36a9c 100644
> --- a/qom/object.c
> +++ b/qom/object.c
> @@ -373,9 +373,8 @@ Object *object_new(const char *typename)
>
> void object_delete(Object *obj)
> {
> + g_assert(obj->ref == 1);
> object_unref(obj);
> - g_assert(obj->ref == 0);
> - g_free(obj);
> }
>
> static bool type_is_ancestor(TypeImpl *type, TypeImpl *target_type)
> @@ -585,6 +584,7 @@ void object_unref(Object *obj)
> /* parent always holds a reference to its children */
> if (obj->ref == 0) {
> object_finalize(obj);
> + g_free(obj);
> }
> }
>
next prev parent reply other threads:[~2012-02-22 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 18:00 [Qemu-devel] [PATCH] qom: Make object_unref() free the object's memory when refcount goes to 0 alexander_barabash
2012-02-22 19:12 ` Anthony Liguori [this message]
2012-02-23 16:21 ` Alexander Barabash
2012-02-24 15:11 ` Anthony Liguori
2012-02-26 9:54 ` Alexander Barabash
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F453E1A.9030701@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alexander_barabash@mentor.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).