[libvirt] [PATCH v9 0/3] DEVICE_DELETED event

2013-03-21 Thread Michael S. Tsirkin
libvirt has a long-standing bug: when removing the device,
it can request removal but does not know when the
removal completes. Add an event so we can fix this in a robust way.

First patch only adds the event with ID, second patch adds a path field.
Split this way for ease of backport (stable downstreams without QOM
would want to only take the first patch).
Event without fields is still useful as management can use it to
poll device list to figure out which device was removed.

Signed-off-by: Michael S. Tsirkin m...@redhat.com

If there are no more comments I'll stick this on my
pci branch.

Changes from v8:
- reorder qom destruction so no need to change unparent 

Changes from v7:
- none, v7 was malformed series sent by mistake

Changes from v6:
- make empty event use data: {}, Markus prefers this

Changes from v5:
- Emit an empty event on unnamed devices in patch 1/3, as suggested by 
Markus

Changes from v4:
- Add extra triggers and extra fields as requested by Markus

Changes from v3:
- Document that we only emit events for devices with
  and ID, as suggested by Markus
Changes from v2:
- move event toward the end of device_unparent,
  so that parents are reported after their children,
  as suggested by Paolo
Changes from v1:
- move to device_unparent
- address comments by Andreas and Eric


-- 
Anthony Liguori


Michael S. Tsirkin (3):
  qdev: DEVICE_DELETED event
  qom: call class destructor before unparent
  qmp: add path to device_deleted event

 QMP/qmp-events.txt| 18 ++
 hw/qdev.c | 14 ++
 include/monitor/monitor.h |  1 +
 monitor.c |  1 +
 qapi-schema.json  |  4 +++-
 qom/object.c  |  6 +++---
 6 files changed, 40 insertions(+), 4 deletions(-)

-- 
MST

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list


Re: [libvirt] [PATCH v9 0/3] DEVICE_DELETED event

2013-03-21 Thread Andreas Färber
Am 21.03.2013 13:07, schrieb Michael S. Tsirkin:
 Changes from v8:
 - reorder qom destruction so no need to change unparent 
 
 Changes from v7:
 - none, v7 was malformed series sent by mistake
 
 Changes from v6:
 - make empty event use data: {}, Markus prefers this
 
 Changes from v5:
 - Emit an empty event on unnamed devices in patch 1/3, as suggested by 
 Markus
 
 Changes from v4:
 - Add extra triggers and extra fields as requested by Markus

Series looks good,

Reviewed-by: Andreas Färber afaer...@suse.de

Andreas

 
 Changes from v3:
 - Document that we only emit events for devices with
   and ID, as suggested by Markus
 Changes from v2:
 - move event toward the end of device_unparent,
   so that parents are reported after their children,
   as suggested by Paolo
 Changes from v1:
 - move to device_unparent
 - address comments by Andreas and Eric

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list