qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gonglei <arei.gonglei@huawei.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] virtio: link the rng backend through an alias property
Date: Wed, 29 Oct 2014 09:27:58 +0800	[thread overview]
Message-ID: <5450429E.6070802@huawei.com> (raw)
In-Reply-To: <1414538251-11428-1-git-send-email-pbonzini@redhat.com>

On 2014/10/29 7:17, Paolo Bonzini wrote:

> The virtio-rng backend is currently linked twice, once in
> virtio-rng-pci/virtio-rng-ccw and once in virtio-rng-device.  This
> causes a double unref of the backend when the parent device is unplugged.
> 
> To fix this, make virtio-rng-pci/virtio-rng-ccw use an alias, similar
> to what is already being done for the iothread link.
> 

I think s390_virtio_rng should also use an alias for rng backend.

Best regards,
-Gonglei

> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  hw/s390x/virtio-ccw.c  | 6 ++----
>  hw/virtio/virtio-pci.c | 7 ++-----
>  2 files changed, 4 insertions(+), 9 deletions(-)
> 
> diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
> index 1c0d913..ea236c9 100644
> --- a/hw/s390x/virtio-ccw.c
> +++ b/hw/s390x/virtio-ccw.c
> @@ -1544,10 +1544,8 @@ static void virtio_ccw_rng_instance_init(Object *obj)
>  
>      virtio_instance_init_common(obj, &dev->vdev, sizeof(dev->vdev),
>                                  TYPE_VIRTIO_RNG);
> -    object_property_add_link(obj, "rng", TYPE_RNG_BACKEND,
> -                             (Object **)&dev->vdev.conf.rng,
> -                             qdev_prop_allow_set_link_before_realize,
> -                             OBJ_PROP_LINK_UNREF_ON_RELEASE, NULL);
> +    object_property_add_alias(obj, "rng", OBJECT(&dev->vdev),
> +                              "rng", &error_abort);
>  }
>  
>  static Property virtio_ccw_rng_properties[] = {
> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> index 542fb9e..e490ade 100644
> --- a/hw/virtio/virtio-pci.c
> +++ b/hw/virtio/virtio-pci.c
> @@ -1525,11 +1525,8 @@ static void virtio_rng_initfn(Object *obj)
>  
>      virtio_instance_init_common(obj, &dev->vdev, sizeof(dev->vdev),
>                                  TYPE_VIRTIO_RNG);
> -    object_property_add_link(obj, "rng", TYPE_RNG_BACKEND,
> -                             (Object **)&dev->vdev.conf.rng,
> -                             qdev_prop_allow_set_link_before_realize,
> -                             OBJ_PROP_LINK_UNREF_ON_RELEASE, NULL);
> -
> +    object_property_add_alias(obj, "rng", OBJECT(&dev->vdev), "rng",
> +                              &error_abort);
>  }
>  
>  static const TypeInfo virtio_rng_pci_info = {

      reply	other threads:[~2014-10-29  1:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 23:17 [Qemu-devel] [PATCH] virtio: link the rng backend through an alias property Paolo Bonzini
2014-10-29  1:27 ` Gonglei [this message]

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=5450429E.6070802@huawei.com \
    --to=arei.gonglei@huawei.com \
    --cc=pbonzini@redhat.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).