On Fri, Jul 13, 2018 at 09:03:12PM +0100, Andrew Cooper wrote: > This is prep work for the following patch - please refer to it as well. > > When auditing and manipulating policies, it is necessary to do so with a > complete set of policies, due to the interdependences of the contents. A > containing structure like this will allow for clearer APIs and code. > > As a first user, this structure is convenient for the mapping used by > XEN_SYSCTL_get_cpu_policy (implemented in the next patch), and for auditing > (later when XEN_DOMCTL_set_cpu_policy is implemented). > > At this point, the distinction between *_max and *_default is introduced into > the ABI. For now, *_default is mapped to *_max, but future development work > will result in *_default being a logical subset of *_max. > > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
Reviewed-by: Wei Liu <wei.l...@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
