From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>, Tim Deegan <tim@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: [PATCH] xen: Fix XSM build following c/s 92942fd
Date: Tue, 9 Feb 2016 16:21:11 +0000 [thread overview]
Message-ID: <1455034871-31743-1-git-send-email-andrew.cooper3@citrix.com> (raw)
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: Jan Beulich <JBeulich@suse.com>
CC: Tim Deegan <tim@xen.org>
CC: Ian Campbell <Ian.Campbell@citrix.com>
CC: Daniel De Graaf <dgdegra@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
next reply other threads:[~2016-02-09 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 16:21 Andrew Cooper [this message]
2016-02-09 17:05 ` [PATCH] xen: Fix XSM build following c/s 92942fd Jan Beulich
2016-02-10 10:39 ` Andrew Cooper
2016-02-10 10:47 ` Jan Beulich
2016-02-11 0:15 ` Daniel De Graaf
2016-02-17 14:21 ` Andrew Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455034871-31743-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).