From: "Daniel P. Berrange" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Programmingkid <programmingkidx@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] monitor: allow object_del & device_del to accept QOM paths
Date: Fri, 28 Aug 2015 13:59:46 +0100 [thread overview]
Message-ID: <20150828125945.GO28526@redhat.com> (raw)
In-Reply-To: <87vbbz8tgq.fsf@blackfin.pond.sub.org>
On Fri, Aug 28, 2015 at 02:53:41PM +0200, Markus Armbruster wrote:
> Copying Andreas and Paolo for QOM expertise.
>
> "Daniel P. Berrange" <berrange@redhat.com> writes:
>
> > Currently both object_del and device_del require that the
> > client provide the object/device short ID. While user
> > creatable objects require an ID to be provided at time of
> > creation, qdev devices may be created without giving an
> > ID. The only unique identifier they would then have is the
> > QOM object path.
> >
> > Allowing device_del to accept an object path ensures all
> > devices are deletable regardless of whether they have an
> > ID.
> >
> > (qemu) device_add usb-mouse
> > (qemu) qom-list /machine/peripheral-anon
> > device[0] (child<usb-mouse>)
> > type (string)
> > (qemu) device_del /machine/peripheral-anon/device[0]
> >
> > Although objects require an ID to be provided upfront,
> > there may be cases where the client would prefer to
> > use QOM paths when deleting.
> >
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
>
> I believe this makes sense no matter what we do about device IDs (see
> thread "Should we auto-generate IDs?").
[snip]
> Update qapi-schema.json updated the obvious way, and you can have my
> R-by. Also addressing my stylistic nitpicks would be nice.
Already posted a v2 with the qapi-schema.json addition after Eric
pointed it out :-)
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2015-08-28 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 15:37 [Qemu-devel] [PATCH] monitor: allow object_del & device_del to accept QOM paths Daniel P. Berrange
2015-08-27 16:01 ` Eric Blake
2015-08-28 0:29 ` Gonglei
2015-08-28 12:53 ` Markus Armbruster
2015-08-28 12:59 ` Daniel P. Berrange [this message]
2015-08-29 6:49 ` Paolo Bonzini
2015-08-29 7:27 ` Gonglei
2015-09-01 8:58 ` Daniel P. Berrange
2015-09-01 9:12 ` Daniel P. Berrange
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=20150828125945.GO28526@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.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 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).