WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH V2 08/11] libxl_qmp, Introduce qmp_request_handle

Anthony PERARD writes ("[Xen-devel] [PATCH V2 08/11] libxl_qmp, Introduce 
qmp_request_handle."):
> This structure helps keep the return code of the callback, so a
> caller can read it.

This is heading in a plausible direction but:

 * You need to state which of the members of the struct are for use by
   which parts of libxl, and when any shared members are written etc.

 * "handle" is the wrong word for this.  "handle" would refer to a
   pointer or perhaps descriptor.  This is a context/info structure.

 * The "free_it" parameter to qmp_send seems odd.  Surely it should
   just be the case that the same person that allocated the context
   should free it ?

Ian.

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

<Prev in Thread] Current Thread [Next in Thread>