qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Andreas Faerber <afaerber@suse.de>,
	Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] qom: link property fixes
Date: Wed, 05 Mar 2014 09:14:11 +0100	[thread overview]
Message-ID: <5316DCD3.3000306@redhat.com> (raw)
In-Reply-To: <1393969512-9468-1-git-send-email-stefanha@redhat.com>

Il 04/03/2014 22:45, Stefan Hajnoczi ha scritto:
> There are two problems with QOM link properties:
>
> 1. There are refcount leaks in many object_property_add_link() callers.
> 2. There is no way to prevent link properties from being set after a device is
>    realized.
>
> This patch series fixes these issues by extending the
> object_property_add_link() function.

Thanks for looking into this!  Just two (mostly) cosmetic comments:

1) in patch 2 we could use a flags argument instead of a "bool".  This 
is more easily extensible and self-documenting.

2) in patch 3 what you're adding is not exactly a setter; it is more 
like a check.  I think we should either switch to a get/set model (more 
consistent with other properties, but more boilerplate too), or rename 
it to something else than "check".

Paolo

> Stefan Hajnoczi (4):
>   qom: split object_property_set_link()
>   qom: make QOM link property unref optional
>   qom: add set() argument to object_property_add_link()
>   virtio-rng: avoid default_backend refcount leak
>
>  hw/core/qdev-properties.c    |  12 ++++
>  hw/core/qdev.c               |   9 ++-
>  hw/dma/xilinx_axidma.c       |  16 ++++--
>  hw/net/xilinx_axienet.c      |  16 ++++--
>  hw/pcmcia/pxa2xx.c           |   5 +-
>  hw/s390x/s390-virtio-bus.c   |   4 +-
>  hw/s390x/virtio-ccw.c        |   4 +-
>  hw/virtio/virtio-pci.c       |   4 +-
>  hw/virtio/virtio-rng.c       |   7 ++-
>  include/hw/qdev-properties.h |  11 ++++
>  include/qom/object.h         |  19 ++++++-
>  qom/object.c                 | 128 ++++++++++++++++++++++++++++++++-----------
>  ui/console.c                 |   4 +-
>  13 files changed, 190 insertions(+), 49 deletions(-)
>

  parent reply	other threads:[~2014-03-05  8:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 21:45 [Qemu-devel] [PATCH 0/4] qom: link property fixes Stefan Hajnoczi
2014-03-04 21:45 ` [Qemu-devel] [PATCH 1/4] qom: split object_property_set_link() Stefan Hajnoczi
2014-03-05  9:26   ` Andreas Färber
2014-03-04 21:45 ` [Qemu-devel] [PATCH 2/4] qom: make QOM link property unref optional Stefan Hajnoczi
2014-03-04 21:45 ` [Qemu-devel] [PATCH 3/4] qom: add set() argument to object_property_add_link() Stefan Hajnoczi
2014-03-04 21:45 ` [Qemu-devel] [PATCH 4/4] virtio-rng: avoid default_backend refcount leak Stefan Hajnoczi
2014-03-05  8:14 ` Paolo Bonzini [this message]
2014-03-05  9:24   ` [Qemu-devel] [PATCH 0/4] qom: link property fixes Andreas Färber
2014-03-05  9:31     ` Paolo Bonzini

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=5316DCD3.3000306@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).