Re: [Xen-devel] [PATCH 0/3] libxl: Permit immediate asynchronous completion

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Jackson writes ("[PATCH 0/3] libxl: Permit immediate asynchronous 
completion"):
> Ian Jackson writes ("Re: [Xen-devel] [PATCH 08/11] libxl: 
> Asynchronous/long-running operation infrastructure"):
> > Yes, you are right, there is a bug in libxl_device_disk_remove /
> > libxl__initiate_device_remove.  I hadn't spotted that the "out" path
> > from the old device removal code was used in a success case too.
> > 
> > I will fix it.
> 
> Please take a look at the following 3-patch series.  I have compiled
> it but not tested it, but I think something like it should work.

Sorry, Roger, the way I sent this mail omitted you from the CC.

>  1/3 libxl: ao: allow immediate completion
>  2/3 libxl: fix hang due to libxl__initiate_device_remove
>  3/3 libxl: Fix eventloop_iteration over-locking
> 
> Hopefully 1/3 and 2/3 will make the intended behaviour, and the
> intended usage clear.  Sorry for confusing you with a bad example!

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel