[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] SSID and CPU pool parsing in xl / libxl
Hi Daniel, Dario, Juergen and others I'm trying to overhaul some libxl infrastructure at the moment, so that we can preserve domain configurations across save and restore. The first step is libxl needs to be able to serialize / deserialize configurations. When I went through the list of xl config file options, most of the options can be easily serialized and sent over the wire to the other end. But SSID parsing and CPU pool ID parsing look exceptional -- they happen in xl (toolstack) level, not libxl (library) level. Take "init_seclabel" as an example, xl calls libxl_flask_context_to_sid to translate a string to an SSID (which is local to host) then passes it to libxl. If libxl serialize its data, then the receiving end only sees the translated SSID, not the "init_seclabel". The string is actually the relavent bit to rebuild a domain, not the SSID (because it's local to host). The same situation applies to CPU pool ID parsing. I plan to push the parsing down to libxl level, but I'm not sure if there's any reason it's done in xl in the first place. Please let me know if you have any concern. Thanks Wei. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |