Re: [Xen-devel] [PATCH 20 of 29 RFC] libxl: introduce libxl hotplug public API functions

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Jackson writes ("Re: [Xen-devel] [PATCH 20 of 29 RFC] libxl: introduce 
libxl hotplug public API functions"):
> Ian Campbell writes ("Re: [Xen-devel] [PATCH 20 of 29 RFC] libxl: introduce 
> libxl hotplug public API functions"):
> > Do you integrate with the libxl event loop? If you did wouldn't this be
> > trivial to handle in xl and wouldn't the xldeviced become the trivial
> > setup + run the event loop program?
> 
> That would be one way to look at it.
> 
>   void libxl_xldeviced_enter(libxl_ctx*); /* never returns */

Actually, thinking about it, the interface is probably:

   int libxl_devicedaemon_start(libxl_ctx*);
     /* Causes this libxl ctx to behave like the xl device daemon
      * whenever it is processing libxl events. */

and then the caller can do this

   rc = libxl_devicedaemon_start(ctx);
   if (rc) ...

   for (;;) {
       ... libxl_event_wait ...   
   }

In principle it would be possible for this device daemon to be part of
some other daemon this way.

Ian.

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