All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: cornelia.huck@de.ibm.com, peter.crosthwaite@xilinx.com,
	Andreas Faerber <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v4 0/9] virtio-blk: use alias properties in transport devices
Date: Tue, 24 Jun 2014 14:22:07 +0200	[thread overview]
Message-ID: <53A96D6F.5010609@redhat.com> (raw)
In-Reply-To: <1403085516-10340-1-git-send-email-stefanha@redhat.com>

Il 18/06/2014 11:58, Stefan Hajnoczi ha scritto:
> v4:
>  * Coding style: typedef struct { on a single line [Andreas]
>  * Add "dataplane: bail out on unsupported transport" for s390-virtio [Cornelia]
>
> v3:
>  * Split qdev_alias_all_properties() into its own patch [Peter Crosthwaite]
>  * Do not dereference DEVICE_CLASS(class) inline [Peter Crosthwaite]
>
> v2:
>  * Add qdev_alias_all_properties() instead of virtio-blk-specific function [Paolo]
>  * Explain refcount handling in doc comment [Paolo]
>  * Fix "property" duplicate typo [Peter Crosthwaite]
>  * Add "the same object or" to clarify commit description [Igor]
>
> Thanks for the feedback on the RFC.  This time around the alias property is
> implemented at the QOM property level instead of at the qdev property level.
>
> Note that this series only addresses virtio-blk.  In later series we can
> convert virtio net, scsi, rng, and serial.
>
> The virtio transport/device split is broken as follows:
>
> 1. The virtio-blk device is never finalized because the transport devices
>    (virtio-blk-pci and friends) leak the refcount.
>
> 2. If we fix the refcount leak then we double-free the 'serial' string property
>    upon hot unplug since its char* is copied into the virtio-blk device which
>    has an identical 'serial' qdev property.
>
> This series solves both of these problems as follows:
>
> 1. Introduce a QOM alias property that lets the transport device forward
>    property accesses into the virtio device (the child).
>
> 2. Use alias properties in transport devices, instead of keeping a duplicate
>    copy of the VirtIOBlkConf struct.
>
> 3. Fix the virtio-blk device refcount leak.  It's now safe to do this since the
>    double-free has been resolved.
>
> Tested that hotplug/hotunplug of virtio-blk-pci still works.
>
> Cornelia Huck (1):
>   dataplane: bail out on unsupported transport
>
> Stefan Hajnoczi (8):
>   qom: add object_property_add_alias()
>   virtio-blk: avoid qdev property definition duplication
>   virtio-blk: move x-data-plane qdev property to virtio-blk.h
>   qdev: add qdev_alias_all_properties()
>   virtio-blk: use aliases instead of duplicate qdev properties
>   virtio-blk: drop virtio_blk_set_conf()
>   virtio: fix virtio-blk child refcount in transports
>   virtio-blk: move qdev properties into virtio-blk.c
>
>  hw/block/dataplane/virtio-blk.c | 10 ++++++++
>  hw/block/virtio-blk.c           | 18 +++++++++------
>  hw/core/qdev.c                  | 21 +++++++++++++++++
>  hw/s390x/s390-virtio-bus.c      | 10 ++------
>  hw/s390x/s390-virtio-bus.h      |  1 -
>  hw/s390x/virtio-ccw.c           |  7 ++----
>  hw/s390x/virtio-ccw.h           |  1 -
>  hw/virtio/virtio-pci.c          |  7 ++----
>  hw/virtio/virtio-pci.h          |  1 -
>  include/hw/qdev-properties.h    |  2 ++
>  include/hw/virtio/virtio-blk.h  | 19 ---------------
>  include/qom/object.h            | 20 ++++++++++++++++
>  qom/object.c                    | 51 +++++++++++++++++++++++++++++++++++++++++
>  13 files changed, 121 insertions(+), 47 deletions(-)
>

Andreas, can you review this series?

Paolo

  parent reply	other threads:[~2014-06-24 12:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  9:58 [Qemu-devel] [PATCH v4 0/9] virtio-blk: use alias properties in transport devices Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 1/9] qom: add object_property_add_alias() Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 2/9] virtio-blk: avoid qdev property definition duplication Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 3/9] dataplane: bail out on unsupported transport Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 4/9] virtio-blk: move x-data-plane qdev property to virtio-blk.h Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 5/9] qdev: add qdev_alias_all_properties() Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 6/9] virtio-blk: use aliases instead of duplicate qdev properties Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 7/9] virtio-blk: drop virtio_blk_set_conf() Stefan Hajnoczi
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 8/9] virtio: fix virtio-blk child refcount in transports Stefan Hajnoczi
2014-06-25  9:25   ` Peter Crosthwaite
2014-06-18  9:58 ` [Qemu-devel] [PATCH v4 9/9] virtio-blk: move qdev properties into virtio-blk.c Stefan Hajnoczi
2014-06-24 12:22 ` Paolo Bonzini [this message]
2014-06-30  8:47 ` [Qemu-devel] [PATCH v4 0/9] virtio-blk: use alias properties in transport devices Stefan Hajnoczi

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=53A96D6F.5010609@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=peter.crosthwaite@xilinx.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.