Koushik Chakravarty writes ("RE: tools/libxl - Async Task Cancellation Query"):
> When you say - " That would require the caller to preserve the ao_how which
> seems awkward to me " - whom do you refer as the caller?
By the caller I mean the program outside libxl which is calling libxl.
> >From
Hi Ian,
Any thoughts on this below?
Regards,
Koushik Chakravarty
Mobile - +91-9663396424
-Original Message-
From: Koushik Chakravarty
Sent: Wednesday, April 8, 2015 5:44 PM
To: Ian Jackson
Cc: Euan Harris; 'xen-de...@lists.xensource.com'
Subject: RE: tools/libxl - Async Task Cancellatio
Thanks Ian for the answers. I have a follow - up on the below:
"Can I suggest adding a unique private 'id' field to the libxl_asyncop_how
structure, that will be populated by AO_CREATE? This will help finding the
matching corresponding libxl_ao from the ctx->aos_inprogress in
libxl_ao_cancel()
Koushik Chakravarty writes ("tools/libxl - Async Task Cancellation Query"):
> I am currently looking into the asynchronous task cancellation in libxl and
> have a few very specific queries, if you could answer.
Sure. Thanks for what has evidently been a careful review of the
code.
> 1.In li
