From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>, yu.c.zhang@linux.intel.com
Cc: andrew.cooper3@citrix.com, Wei Liu <wei.liu2@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: [DO NOT APPLY PATCH XTF 1/2] x86: add UMIP feature bit
Date: Thu, 2 Mar 2017 08:42:31 +0000 [thread overview]
Message-ID: <20170302084232.13339-2-wei.liu2@citrix.com> (raw)
In-Reply-To: <20170302084232.13339-1-wei.liu2@citrix.com>
Strangely there was already one cpu_has_umip defined, so there is no
need for one in this patch.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
include/arch/x86/processor.h | 1 +
include/xen/arch-x86/cpufeatureset.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/include/arch/x86/processor.h b/include/arch/x86/processor.h
index 0106954..e2a2cbb 100644
--- a/include/arch/x86/processor.h
+++ b/include/arch/x86/processor.h
@@ -52,6 +52,7 @@
#define X86_CR4_PCE 0x00000100 /* Performance counters at ipl 3 */
#define X86_CR4_OSFXSR 0x00000200 /* Fast FPU save and restore */
#define X86_CR4_OSXMMEXCPT 0x00000400 /* Unmasked SSE exceptions */
+#define X86_CR4_UMIP 0x00000800 /* UMIP */
#define X86_CR4_VMXE 0x00002000 /* VMX */
#define X86_CR4_SMXE 0x00004000 /* SMX */
#define X86_CR4_FSGSBASE 0x00010000 /* {rd,wr}{fs,gs}base */
diff --git a/include/xen/arch-x86/cpufeatureset.h b/include/xen/arch-x86/cpufeatureset.h
index 905e8e8..f66a4ab 100644
--- a/include/xen/arch-x86/cpufeatureset.h
+++ b/include/xen/arch-x86/cpufeatureset.h
@@ -144,6 +144,7 @@
/* Intel-defined CPU features, CPUID level 0x00000007:0.ecx, word 6 */
#define X86_FEATURE_PREFETCHWT1 (6*32+ 0) /* PREFETCHWT1 instruction */
+#define X86_FEATURE_UMIP (6*32+ 2) /* User-Mode Instruction Prevention */
#define X86_FEATURE_PKU (6*32+ 3) /* Protection Keys for Userspace */
#define X86_FEATURE_OSPKE (6*32+ 4) /* OS Protection Keys Enable */
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-02 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 2:33 About UMIP unit test Yu Zhang
2017-03-02 8:06 ` Andrew Cooper
2017-03-02 8:42 ` [DO NOT APPLY PATCH XTF 0/2] UMIP test case Wei Liu
2017-03-02 8:42 ` Wei Liu [this message]
2017-03-02 8:42 ` [DO NOT APPLY PATCH XTF 2/2] Add UMIP test Wei Liu
2017-03-02 9:05 ` [DO NOT APPLY PATCH XTF 0/2] UMIP test case Andrew Cooper
2017-03-02 10:53 ` Wei Liu
2017-03-02 12:30 ` Yu Zhang
2017-03-02 12:39 ` 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=20170302084232.13339-2-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yu.c.zhang@linux.intel.com \
/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).