In practice, aborting this task will cause all subsequent actual
backend operations to fail, but will not actually cause the
libxl_device_events_handler operation to complete.
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
CC: Roger Pau Monné <roger....@citrix.com>
Acked-by: Roger Pau Monné <roger....@citrix.com>
Acked-by: Ian Campbell <ian.campb...@citrix.com>
---
v2: New in this version of the series.
---
tools/libxl/libxl.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/libxl/libxl.h b/tools/libxl/libxl.h
index e52afca..a556374 100644
--- a/tools/libxl/libxl.h
+++ b/tools/libxl/libxl.h
@@ -1425,6 +1425,9 @@ libxl_device_pci *libxl_device_pci_list(libxl_ctx *ctx,
uint32_t domid,
* From a libxl API point of view, this starts a long-running
* operation. That operation consists of "being a driver domain"
* and never completes.
+ *
+ * Attempting to abort this operation is not advisable; proper
+ * shutdown of the driver domain task is not supported.
*/
int libxl_device_events_handler(libxl_ctx *ctx,
const libxl_asyncop_how *ao_how)
--
1.7.10.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
