On Fri, Oct 03, 2008 at 07:45:24AM -0700, Dan Smith wrote:
DV> creating a domain is always the trickiest part of domain
lifecycle
DV> and setting up the framework is often something a bit obfuscated,
DV> nearly by definition. But if we could associate meaningful
DV> constants to the device policies here, this would help people
DV> having to improve or debug that code in the future ;-)
Okay, I suppose that if the QEMU driver ends up doing something
similar, the constants would be reused.
Should they go in cgroup.h since they're expected to be used with that
interface?
Fine by me, but I'm more looking to being able to map semantic
to the value than sharing the values at this point,
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit
http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine
http://rpmfind.net/
http://veillard.com/ | virtualization library
http://libvirt.org/