[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
Roger Pau Monne writes ("[Xen-devel] [PATCH 20 of 29 RFC] libxl: introduce libxl hotplug public API functions"): > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid> > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/mtu > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/model > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/mac > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/ip > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/bridge > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/ifname > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/script > /hotplug/<backend_domid>/<frontend_domid>/vif/<devid>/nictype > > This will allow us to pass the libxl_device_disk and libxl_device_nic > struct from Dom0 to driver domain, and execute the necessary backends > there. Also I think as you're inventing a new protocol we should have a protocol document which, unless I've missed it, doesn't appear in your series. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |