[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4] monitor: allow device_del to accept QOM path
From: |
Eric Blake |
Subject: |
Re: [Qemu-devel] [PATCH v4] monitor: allow device_del to accept QOM paths |
Date: |
Mon, 14 Sep 2015 10:41:04 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 |
On 09/14/2015 10:17 AM, Programmingkid wrote:
>
> On Sep 14, 2015, at 11:53 AM, Markus Armbruster wrote:
>
>> "Daniel P. Berrange" <address@hidden> 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
signature.asc
Description: OpenPGP digital signature