Re: [Qemu-devel] [PATCH for-2.10 3/3] qdev: defer DEVICE_DEL event until instance_finalize()

2017-10-06 Thread Michael Roth
Quoting Auger Eric (2017-08-09 09:04:54) > Hi Michael, > > On 27/07/2017 03:30, Michael Roth wrote: > > DEVICE_DEL is currently emitted when a Device is unparented, as > > opposed to when it is finalized. The main design motivation for this > > seems to be that after unparent()/unrealize(), the

Re: [Qemu-devel] [PATCH for-2.10 3/3] qdev: defer DEVICE_DEL event until instance_finalize()

2017-08-09 Thread Auger Eric
Hi Michael, On 27/07/2017 03:30, Michael Roth wrote: > DEVICE_DEL is currently emitted when a Device is unparented, as > opposed to when it is finalized. The main design motivation for this > seems to be that after unparent()/unrealize(), the Device is no > longer visible to the guest, and thus

Re: [Qemu-devel] [PATCH for-2.10 3/3] qdev: defer DEVICE_DEL event until instance_finalize()

2017-07-31 Thread Greg Kurz
On Wed, 26 Jul 2017 20:30:55 -0500 Michael Roth wrote: > DEVICE_DEL is currently emitted when a Device is unparented, as > opposed to when it is finalized. The main design motivation for this > seems to be that after unparent()/unrealize(), the Device is no > longer

[Qemu-devel] [PATCH for-2.10 3/3] qdev: defer DEVICE_DEL event until instance_finalize()

2017-07-26 Thread Michael Roth
DEVICE_DEL is currently emitted when a Device is unparented, as opposed to when it is finalized. The main design motivation for this seems to be that after unparent()/unrealize(), the Device is no longer visible to the guest, and thus the operation is complete from the perspective of management.