qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Programmingkid <programmingkidx@gmail.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] monitor: allow object_del & device_del to accept QOM paths
Date: Thu, 27 Aug 2015 10:01:12 -0600	[thread overview]
Message-ID: <55DF3448.5070302@redhat.com> (raw)
In-Reply-To: <1440689864-32127-1-git-send-email-berrange@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

On 08/27/2015 09:37 AM, Daniel P. Berrange wrote:
> 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>
> ---
>  hmp-commands.hx |  6 ++++--
>  qdev-monitor.c  | 14 +++++++++-----
>  qmp-commands.hx | 17 +++++++++++++----
>  qmp.c           | 10 +++++++---
>  4 files changed, 33 insertions(+), 14 deletions(-)

Might also want to touch qapi-schema.json for consistent documentation
of the @id parameter (our goal is for qmp-commands.hx to go away some
day; and while we can merge contents at that time, it's nicer to keep
them in sync now)

Reviewed-by: Eric Blake <eblake@redhat.com

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-08-27 16:01 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 [this message]
2015-08-28  0:29 ` Gonglei
2015-08-28 12:53 ` Markus Armbruster
2015-08-28 12:59   ` Daniel P. Berrange
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=55DF3448.5070302@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@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).