qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] monitor: allow object_del & device_del to accept QOM paths
Date: Thu, 27 Aug 2015 13:11:34 -0600	[thread overview]
Message-ID: <55DF60E6.70408@redhat.com> (raw)
In-Reply-To: <4E89D25A-1DA7-4D4E-B1AF-453CA3227BFD@gmail.com>

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

On 08/27/2015 11:26 AM, Programmingkid wrote:
> 
> On Aug 27, 2015, at 12:13 PM, 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]

> Your patch do the job, but could be tweaked. Could we make an alias for
> "qom-list /machine/peripheral-anon" that is actually easy to remember. Perhaps "info devices". 
> 
> Also typing "device_del /machine/peripheral-anon/device[0]" seems unnecessary. It probably 
> could be shortened to just "device_del device[0]". 

You're welcome to submit follow up patches to make HMP more useful to
you ('info' is already an HMP command, so adding an 'info devices'
submode is a reasonable addition).  However, the important change here
is the QMP change that management apps, like libvirt, will use; and that
interface does not need further syntactic sugar.  The patch specifically
distinguishes between full QOM paths (leading '/') and short names (no
leading '/'); and your proposal to try the QOM path under
/machine/peripheral-anon/ when given just the string 'device[0]' that
did not resolve to a short name is counter to that distinguishing
factor.  Besides, management apps don't care how long a string is.  The
QMP interface should not be changed, and any such simplifications you
write a patch for should be limited to the HMP side.

-- 
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 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 16:13 [Qemu-devel] [PATCH v2] monitor: allow object_del & device_del to accept QOM paths Daniel P. Berrange
2015-08-27 16:22 ` Eric Blake
2015-08-27 17:26 ` Programmingkid
2015-08-27 19:11   ` Eric Blake [this message]
2015-08-28  8:45   ` Daniel P. Berrange
2015-08-28  0:40 ` Gonglei
2015-08-28 12:59 ` Markus Armbruster

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=55DF60E6.70408@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).