Re: [Qemu-devel] [RFC PATCH 0/2] Early release of -drive QemuOpts

2016-02-04 Thread Paolo Bonzini
On 22/01/2016 23:38, Max Reitz wrote: > On 22.01.2016 15:01, Paolo Bonzini wrote: >> >> >> On 08/01/2016 18:37, Paolo Bonzini wrote: >>> In short, this patch gets rid of blockdev_mark_auto_del and >>> blockdev_auto_del. >>> >>> With these patches, it is possible to create a new -drive with the sa

Re: [Qemu-devel] [RFC PATCH 0/2] Early release of -drive QemuOpts

2016-01-22 Thread Max Reitz
On 22.01.2016 15:01, Paolo Bonzini wrote: > > > On 08/01/2016 18:37, Paolo Bonzini wrote: >> In short, this patch gets rid of blockdev_mark_auto_del and >> blockdev_auto_del. >> >> With these patches, it is possible to create a new -drive with the same >> id as soon as the DEVICE_DELETED event is

Re: [Qemu-devel] [RFC PATCH 0/2] Early release of -drive QemuOpts

2016-01-22 Thread Paolo Bonzini
On 08/01/2016 18:37, Paolo Bonzini wrote: > In short, this patch gets rid of blockdev_mark_auto_del and > blockdev_auto_del. > > With these patches, it is possible to create a new -drive with the same > id as soon as the DEVICE_DELETED event is delivered (which equals to > unrealize). > > I'm s

[Qemu-devel] [RFC PATCH 0/2] Early release of -drive QemuOpts

2016-01-08 Thread Paolo Bonzini
In short, this patch gets rid of blockdev_mark_auto_del and blockdev_auto_del. With these patches, it is possible to create a new -drive with the same id as soon as the DEVICE_DELETED event is delivered (which equals to unrealize). I'm sorry I'm not able to explain the history (and probably do no