All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel@lists.xenproject.org, Juergen Gross <jgross@suse.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v2] xen: use qdev_unplug() instead of g_free() in xen_pv_find_xendev()
Date: Wed, 1 Feb 2017 20:20:57 +0000	[thread overview]
Message-ID: <CAFEAcA_ZxP8iq-vcuBHUzVa7EmjCtqyZ6t8Meu1ypyusnJYACA__44368.25391972$1485980545$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1702011134020.17946@sstabellini-ThinkPad-X260>

On 1 February 2017 at 19:37, Stefano Stabellini <sstabellini@kernel.org> wrote:
> Hi Peter,
>
> do you think this is acceptable?

The set of operations here is basically what I suggested
in review of v1, so I think it is the right thing.
OTOH this is a bit of an odd corner of the QOM model
so it might be worth doing some testing to make sure
the reference counts are doing what you (I) expect and
that the object does get correctly freed both in the
error-handling path here and when the device is
unplugged via xen_pv_del_xendev().

thanks
-- PMM

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-02-01 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01  6:52 [Qemu-devel] [PATCH v2] xen: use qdev_unplug() instead of g_free() in xen_pv_find_xendev() Juergen Gross
2017-02-01 19:37 ` Stefano Stabellini
2017-02-01 20:20   ` Peter Maydell
2017-02-02 10:22     ` Juergen Gross
2017-02-02 10:22     ` [Qemu-devel] " Juergen Gross
2017-02-02 18:23       ` Stefano Stabellini
2017-02-02 18:23       ` [Qemu-devel] " Stefano Stabellini
2017-02-01 20:20   ` Peter Maydell [this message]
2017-02-01 19:37 ` Stefano Stabellini
  -- strict thread matches above, loose matches on Subject: below --
2017-02-01  6:52 Juergen Gross

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='CAFEAcA_ZxP8iq-vcuBHUzVa7EmjCtqyZ6t8Meu1ypyusnJYACA__44368.25391972$1485980545$gmane$org@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=anthony.perard@citrix.com \
    --cc=jgross@suse.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 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.