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?
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com