On Mon, May 23, 2016 at 10:51:29AM -0400, Daniel De Graaf wrote: > This includes the policy in tools/flask/policy in the hypervisor so that > the bootloader does not need to load a policy to get sane behavior from > an XSM-enabled hypervisor. > > RFC because this adds a binding between xen's build and the tools build. > The inclusion of policy.o could be made conditional on a Kconfig option > (the code handles omission of the policy properly) to disable it. ARM > build is also untested. > [...] > +POLICY_SRC := $(XEN_ROOT)/tools/flask/policy/xenpolicy-$(XEN_FULLVERSION)
This (hypervisor build now depends on tools build) needs to be reflected in Makfile target dependency if we're really going to do it. But I think it would make sense to just move the policy directory to hypervisor directory as well, leaving only flask/utils under tools. Just my 2 cents. Wei. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
