From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>,
Markus Armbruster <armbru@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v4] monitor: allow device_del to accept QOM paths
Date: Mon, 14 Sep 2015 10:41:04 -0600 [thread overview]
Message-ID: <55F6F8A0.50800@redhat.com> (raw)
In-Reply-To: <3FBFD05D-A0A4-4A2C-A235-39923ECA7FAE@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
On 09/14/2015 10:17 AM, Programmingkid wrote:
>
> On Sep 14, 2015, at 11:53 AM, Markus Armbruster wrote:
>
>> "Daniel P. Berrange" <berrange@redhat.com> writes:
>>
>>> Currently device_del requires that the client provide the
>>> device short ID. device_add allows devices may be created
>>
>> "allows devices to be created"
>>
>> Could perhaps be touched up on commit.
>>
>>> without giving an ID, at which point there is no way to
>>> delete them with device_del. The QOM object path, however,
>>> provides an alternative way to identify the devices.
>>>
>> If neither Andreas nor Paolo objects, I'd be willing to take this
>> through my tree.
>
> If you do accept this patch, would you still be willing to
> accept an auto-generated ID patch still?
The two are orthogonal. Deleting by QOM path is useful even if all
devices are given an id, and auto-generating an id may be useful to
human users (even though libvirt won't rely on it) regardless of whether
deleting devices by QOM path is in the tree.
But you are worrying about nothing; although Kevin is waiting for a v3,
he has already mentioned on v2 that he is ready to queue auto-generation
once it works:
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg00877.html
--
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 --]
next prev parent reply other threads:[~2015-09-14 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 12:33 [Qemu-devel] [PATCH v4] monitor: allow device_del to accept QOM paths Daniel P. Berrange
2015-09-11 12:46 ` Eric Blake
2015-09-14 15:53 ` Markus Armbruster
2015-09-14 16:17 ` Programmingkid
2015-09-14 16:41 ` Eric Blake [this message]
2015-09-14 16:49 ` Programmingkid
2015-09-14 17:08 ` Eric Blake
2015-09-14 16:43 ` Markus Armbruster
2015-09-14 16:54 ` Programmingkid
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=55F6F8A0.50800@redhat.com \
--to=eblake@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).