[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

On Tue, 2012-02-21 at 16:42 +0000, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 20 of 29 RFC] libxl: 
> introduce libxl hotplug public API functions"):
> > On Tue, 14 Feb 2012, Ian Campbell wrote:
> > > I was wondering if perhaps xl/libxl should handle these events by
> > > default (using the same APIs as xldeviced uses) such that in the simple
> > > case users can continue to just use xl without worrying about
> > > configuring or enabling additional daemons. There would then be an
> > > option to disable this if you were running xldeviced (either in dom0 or
> > > in a driver dom). Perhaps a more DWIM extension would be to default to
> > > running things within xl/libxl only if the backend is in dom0 and assu,e
> > > xldeviced is running in backend doms != 0.
> > 
> > While I understand that technically is not difficult to achieve and
> > doesn't add much complexity in terms of lines of code; starting daemons
> > is cheap and is taken care by xencommons. I am not sure if it is worth
> > introducing yet another way of doing the same thing.
> This is a good point.  Also, if anyone does object to this daemon, and
> we take the event-driven approach already suggested, it probably won't
> be too hard to add later the short-cut to run it in-process.
> So I think for now we should just have the daemonic version.

If the smarts are all in libxl and the daemon is the noddy event loop
then that's ok with me too.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.