qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	libvir-list@redhat.com, "Stefan Hajnoczi" <stefanha@gmail.com>,
	qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Luiz Capitulino" <lcapitulino@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v4] qdev: DEVICE_DELETED event
Date: Mon, 11 Mar 2013 14:26:58 -0500	[thread overview]
Message-ID: <87620xrb3x.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130311173929.GA29465@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> writes:

> On Fri, Mar 08, 2013 at 07:36:28AM -0600, Anthony Liguori wrote:
>> Markus Armbruster <armbru@redhat.com> writes:
>> 
>> > "Michael S. Tsirkin" <mst@redhat.com> writes:
>> >
>> >> On Thu, Mar 07, 2013 at 08:57:52PM +0100, Markus Armbruster wrote:
>> >>> "Michael S. Tsirkin" <mst@redhat.com> writes:
>> >>> 
>> >>> > libvirt has a long-standing bug: when removing the device,
>> >>> > it can request removal but does not know when the
>> >>> > removal completes. Add an event so we can fix this in a robust way.
>> >>> >
>> >>> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>> >>> 
>> >>> Speaking as the acting QMP maintainer, just to avoid misunderstandings:
>> >>> there's disagreement on the event's design, namely when it should fire,
>> >>> and how it should name the device.  I don't want the discussion
>> >>> preempted by a commit.
>> >>
>> >> Yes, you are asking for more functionality, but can I add this in a
>> >> follow-up commit please?  I prefer this patch as is, as it can be
>> >> backported to stable branches and downstreams.  Upstream a follow up
>> >> patch can add fields and more triggers which won't apply to any
>> >> downstreams.
>> >
>> > If you want to address my review comments in a separate patch, go right
>> > ahead.  Please post both together as a series, for coherent review and
>> > to simplify patch tracking.
>> >
>> > I'm asking for two things:
>> >
>> > 1. Event member path.  Fair to call this "more functionality".  I agree
>> >    that backporting it to pre-QOM versions isn't practical.
>> >
>> > 2. Sane event trigger condition: on any device deletion, not just when
>> >    the device happens to have a qdev ID.  This isn't "more", it's
>> >    "different".
>> 
>> Ack.
>> 
>> Regards,
>> 
>> Anthony Liguori
>
>
> So how does one get the path that you require?
>
> ERROR:qom/object.c:1011:object_get_canonical_path: assertion failed:
> (prop != NULL)

Can you share your patch?  This means something is wrong.  All devices
have a canonical path.

Regards,

Anthony Liguori

  reply	other threads:[~2013-03-11 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 18:46 [Qemu-devel] [PATCH v4] qdev: DEVICE_DELETED event Michael S. Tsirkin
2013-03-07 19:57 ` Markus Armbruster
2013-03-07 20:23   ` Michael S. Tsirkin
2013-03-08  7:58     ` Markus Armbruster
2013-03-08 13:36       ` Anthony Liguori
2013-03-11 17:39         ` Michael S. Tsirkin
2013-03-11 19:26           ` Anthony Liguori [this message]
2013-03-11 19:35             ` Michael S. Tsirkin
2013-03-10  9:30       ` Michael S. Tsirkin

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=87620xrb3x.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).