From 2d027f59429bb5426f4b799745bed48832a587cc Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Mon, 25 Nov 2013 11:53:28 +0000 Subject: [PATCH] libxl: doc comment: clarify SIGCHLD demultiplexing requirements Update the comment to clarify that libxl_sigchld_owner_libxl_always implies having only one libxl_ctx, and that libxl_sigchld_owner_mainloop requires one call to libxl_childproc_exited per ctx. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- tools/libxl/libxl_event.h | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/tools/libxl/libxl_event.h b/tools/libxl/libxl_event.h index 27a65dce92..6261f99eb2 100644 --- a/tools/libxl/libxl_event.h +++ b/tools/libxl/libxl_event.h @@ -446,13 +446,16 @@ void libxl_osevent_occurred_timeout(libxl_ctx *ctx, void *for_libxl) * * libxl_sigchld_owner_mainloop: * The application must install a SIGCHLD handler and reap (at - * least) all of libxl's children and pass their exit status - * to libxl by calling libxl_childproc_exited. + * least) all of libxl's children and pass their exit status to + * libxl by calling libxl_childproc_exited. (If the application + * has multiple libxl ctx's, it must call libxl_childproc_exited + * on each ctx.) * * libxl_sigchld_owner_libxl_always: * The application expects libxl to reap all of its children, * and provides a callback to be notified of their exit - * statues. + * statues. The application must have only one libxl_ctx + * configured this way. * * An application which fails to call setmode, or which passes 0 for * hooks, while it uses any libxl operation which might -- 2.39.5