On 06/17/2016 01:14 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Jun 17, 2016 at 01:04:01PM -0400, Daniel De Graaf wrote:
On 06/17/2016 11:50 AM, Konrad Rzeszutek Wilk wrote:
On Thu, Jun 09, 2016 at 10:47:15AM -0400, Daniel De Graaf wrote:
Since FLASK is the only implementation of XSM hooks in Xen, using an
iterated initcall dispatch for setup is overly complex. Change this to
As such, should the Kconfig file enable the FLASK by default?
Or make the XSM entry have the configuration for FLASK?
Or perhaps make the FLASK be the visible one and select XSM?
XSM has previously been the configuration option to enable. If XSM is
enabled (by choice), FLASK will then be enabled by default.
Ah, OK. I need to check, but could you disable FLASK and still have XSM enabled?
Yes, but it won't do anything except slow down the hypervisor a bit.
It's the same behavior as enabling flask and passing "flask=disabled" on
the hypervisor command line.
If someone wanted to write another XSM implementation (or resurrect the
old ACM module), this would be the starting point for that.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
