Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
---
CC: Jan Beulich <jbeul...@suse.com>
CC: Tim Deegan <t...@xen.org>
CC: Ian Campbell <ian.campb...@citrix.com>
CC: Daniel De Graaf <dgde...@tycho.nsa.gov>
Is this actually an appropraite fix? Software relying on -ENOSYS for Xen
feature detection is going to break when running under an XSM hypervisor.
---
xen/xsm/flask/hooks.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/xen/xsm/flask/hooks.c b/xen/xsm/flask/hooks.c
index 9b7de30..f63c3e2 100644
--- a/xen/xsm/flask/hooks.c
+++ b/xen/xsm/flask/hooks.c
@@ -1421,7 +1421,6 @@ static int flask_shadow_control(struct domain *d,
uint32_t op)
break;
case XEN_DOMCTL_SHADOW_OP_ENABLE:
case XEN_DOMCTL_SHADOW_OP_ENABLE_TEST:
- case XEN_DOMCTL_SHADOW_OP_ENABLE_TRANSLATE:
case XEN_DOMCTL_SHADOW_OP_GET_ALLOCATION:
case XEN_DOMCTL_SHADOW_OP_SET_ALLOCATION:
perm = SHADOW__ENABLE;
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
