KVM: Support Intel KeyLocker
cover KVM: Support Intel KeyLocker
This patch set is to enable KVM virtualization of Key Locker feature [1][2].
Key Locker provides a mechanism to encrypt and decrypt data with an AES key without having access to the raw key value by converting AES keys into "handles".
Handles are essentially an encrypted form of those underlying real AES keys. "IWKey (Internal Wrapping Key)", loaded inside CPU, inaccessible from SW, is the key used to seal real AES Keys into handles.
Thus, a real AES Key exists in memory for only a short period of time, when user is requesting a 'handle' from it. After that, the real AES Key can be erased, user then uses handle, with new Key Locker instructions, to perform AES encryption/decryption. By OS policy, usually, handles will be revoked after reboot, then any handles that may have been stolen should no longer be useful to the attacker after the reboot.
IWKey, is the core of this framework. It is loaded into CPU by LOADIWKEY instruction, then inaccessible from (CPU) outside anymore. LOADIWKEY is the only Key Locker instruction that will cause VM-exit (if we set so in VM Execution Control). When load IWKey into CPU, we can ask CPU further randomize it, if HW supports this.
The IWKey can also be distributed among CPUs, rather than LOADIWKEY on each CPU, by: first backup IWKey to platform specific storage, then copy it on target CPU. The backup process is triggered by writing to MSR IA32_COPY_LOCAL_TO_PLATFORM. The restore process is triggered by writing to MSR IA32_COPY_PLATFORM_LOCAL.
Virtualization Design
Key Locker Spec [2] indicates virtualization limitations by current HW implementation.
1) IWKey cannot be read from CPU after it's loaded (this is the nature of this feature) and only 1 copy of IWKey inside 1 CPU.
2) Initial implementations may take a significant amount of time to perform a copy of IWKeyBackup to IWKey (via a write to MSR IA32_COPY_PLATFORM_LOCAL) so it may cause a significant performance impact to reload IWKey after each VM exit.
Due to above reasons, virtualization design makes below decisions
1) don't expose HW randomize IWKey capability (CPUID.0x19.ECX[1]) to guest. As such, guest IWKey cannot be preserved by VMM across VM-{Exit, Entry}. (VMM cannot know what exact IWKey were set by CPU)
2) guests and host can only use Key Locker feature exclusively. [4]
The virtualization implementation is generally straight forward
1) On VM-Exit of guest 'LOADIWKEY', VMM stores the IWKey in vCPU scope area (kvm_vcpu_arch)
2) Right before VM-Entry, VMM load that vCPU's IWKey in to pCPU, by LOADIWKEY instruction.
3) On guest backup local to platform operation, VMM traps the write to MSR, and simulate the IWKey store process by store it in a KVM scope area (kvm_arch), mark the success status in the shadow msr_ia32_iwkey_backup_status and msr_ia32_copy_status.
4) On guest copy from platform to local operation, VMM traps the write to MSR and simulate the process by load kvm_arch.iwkey_backup to vCPU.iwkey; and simulate the success status in the
shadow msr_ia32_copy_status.
5) Guest read the 2 status MSRs will also be trapped and return the shadow value.
6) Other Key Locker instructions can run without VM-Exit in non-root mode.
At the end, we don't suggest this feature to be migratable, as if so, IWKey would have to be exposed to user space, which would weaken this feature's security significance.
BTW, this patch set is based on Kernel v5.10 (2c85ebc) + Kernel Key Locker enabling patches [3].
[1] Intel Architecture Instruction Set Extensions Programming Reference:
https://software.intel.com/content/www/us/en/develop/download/intel-architecture-instruction-set-extensions-programming-reference.html
[2] Intel Key Locker Specification:
https://software.intel.com/content/www/us/en/develop/download/intel-key-locker-specification.html
[3] Kernel enablement patch:
https://lore.kernel.org/lkml/[email protected]/
[4] It's possible to use Key Locker by both the guest and host, albeit with reduced security benefits. I.e., store host IWKey in VMM scoped place (memory/register), VMM switches host-IWKey and guest-IWKey between VM-{Exit/Entry} by LOADIWKEY instruction.
But in this case, an adversary that can observe arbitrary VMM memory may be able to steal both the handles and IWKey. And this case also require the VMM to be running before the first IWKey load.
Robert Hoo (12):
x86/keylocker: Move LOADIWKEY opcode definition from keylocker.c to
keylocker.h
x86/cpufeature: Add CPUID.19H:{EBX,ECX} cpuid leaves kvm/vmx: Introduce the new tertiary processor-based VM-execution
controls
kvm/vmx: enable LOADIWKEY vm-exit support in tertiary processor-based
VM-execution controls
kvm/vmx: Add KVM support on KeyLocker operations kvm/cpuid: Enumerate KeyLocker feature in KVM kvm/vmx/nested: Support new IA32_VMX_PROCBASED_CTLS3 vmx feature
control MSR
kvm/vmx: Refactor vmx_compute_tertiary_exec_control() kvm/vmx/vmcs12: Add Tertiary Exec-Control field in vmcs12 kvm/vmx/nested: Support tertiary VM-Exec control in vmcs02 kvm/vmx/nested: Support CR4.KL in nested
kvm/vmx/nested: Enable nested LOADIWKey VM-exit
arch/x86/include/asm/cpufeature.h | 6 +- arch/x86/include/asm/cpufeatures.h | 11 +- arch/x86/include/asm/disabled-features.h | 2 +- arch/x86/include/asm/keylocker.h | 2 + arch/x86/include/asm/kvm_host.h | 24 ++- arch/x86/include/asm/msr-index.h | 1 + arch/x86/include/asm/required-features.h | 2 +- arch/x86/include/asm/vmx.h | 9 ++ arch/x86/include/asm/vmxfeatures.h | 6 +- arch/x86/include/uapi/asm/vmx.h | 5 +- arch/x86/kernel/cpu/common.c | 7 + arch/x86/kernel/cpu/feat_ctl.c | 9 ++ arch/x86/kernel/keylocker.c | 1 - arch/x86/kvm/cpuid.c | 26 +++- arch/x86/kvm/cpuid.h | 2 + arch/x86/kvm/vmx/capabilities.h | 9 ++ arch/x86/kvm/vmx/nested.c | 34 +++- arch/x86/kvm/vmx/nested.h | 7 + arch/x86/kvm/vmx/vmcs.h | 1 + arch/x86/kvm/vmx/vmcs12.c | 1 + arch/x86/kvm/vmx/vmcs12.h | 3 +- arch/x86/kvm/vmx/vmx.c | 258 ++++++++++++++++++++++++++++++- arch/x86/kvm/vmx/vmx.h | 9 ++ arch/x86/kvm/x86.c | 6 +- arch/x86/kvm/x86.h | 2 + 25 files changed, 422 insertions(+), 21 deletions(-)
Signature · 1 line
1.8.3.1
RFC PATCH 1/12 x86/keylocker: Move LOADIWKEY opcode definition from keylocker.c to keylocker.h
For later kvm part code easy referrence.
--- arch/x86/include/asm/keylocker.h | 2 ++ arch/x86/kernel/keylocker.c | 1 - 2 files changed, 2 insertions(+), 1 deletion(-)
arch/x86/include/asm/keylocker.h +2 -0
@@ -8,6 +8,8 @@#include <linux/bits.h> #include <asm/msr.h> +#define LOADIWKEY ".byte 0xf3,0x0f,0x38,0xdc,0xd1" +#define KEYLOCKER_CPUID 0x019#define KEYLOCKER_CPUID_EAX_SUPERVISOR BIT(0)#define KEYLOCKER_CPUID_EBX_AESKLE BIT(0)
arch/x86/kernel/keylocker.c +0 -1
@@ -40,7 +40,6 @@ bool check_keylocker_readiness(void) }/* Load Internal (Wrapping) Key */ -#define LOADIWKEY ".byte 0xf3,0x0f,0x38,0xdc,0xd1"#define LOADIWKEY_NUM_OPERANDS 3#define LOADIWKEY_HWRAND_RETRY 10
Signature · 1 line
1.8.3.1
RFC PATCH 2/12 x86/cpufeature: Add CPUID.19H:{EBX,ECX} cpuid leaves
In reply to Robert HooThough KeyLocker is generally enumerated by CPUID.(07H,0):ECX.KL[bit23], CPUID.19H:{EBX,ECX} enumerate more details of KeyLocker supporting status.
CPUID.19H:EBX
bit0 enumerates if OS (CR4.KeyLocker) and BIOS have enabled KeyLocker. bit2 enumerates if wide Key Locker instructions are supported. bit4 enumerates if IWKey backup is supported.
CPUID.19H:ECX
bit0 enumerates if the NoBackup parameter to LOADIWKEY is supported. bit1 enumerates if IWKey randomization is supported.
Define these 2 cpuid_leafs so that get_cpu_cap() will have these capabilities included, which will be the knowledge source of KVM on host KeyLocker capabilities.
Most of above features don't have the necessity to appear in /proc/cpuinfo, except "iwkey_rand", which we think might be interesting for user to easily know if his system is using randomized IWKey.
--- arch/x86/include/asm/cpufeature.h | 6 ++++-- arch/x86/include/asm/cpufeatures.h | 11 ++++++++++- arch/x86/include/asm/disabled-features.h | 2 +- arch/x86/include/asm/required-features.h | 2 +- arch/x86/kernel/cpu/common.c | 7 +++++++ 5 files changed, 23 insertions(+), 5 deletions(-)
arch/x86/include/asm/cpufeature.h +4 -2
@@ -30,6 +30,8 @@ enum cpuid_leafsCPUID_7_ECX ,CPUID_8000_0007_EBX ,CPUID_7_EDX , +CPUID_19_EBX , + CPUID_19_ECX, };#ifdef CONFIG_X86_FEATURE_NAMES
@@ -89,7 +91,7 @@ enum cpuid_leafs CHECK_BIT_IN_MASK_WORD(REQUIRED_MASK, 17, feature_bit) || \ CHECK_BIT_IN_MASK_WORD(REQUIRED_MASK, 18, feature_bit) || \ REQUIRED_MASK_CHECK || \ - BUILD_BUG_ON_ZERO(NCAPINTS != 19)) + BUILD_BUG_ON_ZERO(NCAPINTS != 21))#define DISABLED_MASK_BIT_SET (feature_bit) \ ( CHECK_BIT_IN_MASK_WORD(DISABLED_MASK, 0, feature_bit) || \
@@ -112,7 +114,7 @@ enum cpuid_leafs CHECK_BIT_IN_MASK_WORD(DISABLED_MASK, 17, feature_bit) || \ CHECK_BIT_IN_MASK_WORD(DISABLED_MASK, 18, feature_bit) || \ DISABLED_MASK_CHECK || \ - BUILD_BUG_ON_ZERO(NCAPINTS != 19)) + BUILD_BUG_ON_ZERO(NCAPINTS != 21))#define cpu_has (c, bit) \ (__builtin_constant_p(bit) && REQUIRED_MASK_BIT_SET(bit) ? 1 : \
arch/x86/include/asm/cpufeatures.h +10 -1
@@ -13,7 +13,7 @@/* * Defines x86 CPU feature bits */ -#define NCAPINTS 19/* N 32-bit words worth of info */ +#define NCAPINTS 21/* N 32-bit words worth of info */ #define NBUGINTS 1/* N 32-bit bug flags */ /*
@@ -382,6 +382,15 @@#define X86_FEATURE_CORE_CAPABILITIES (18*32+30)/* "" IA32_CORE_CAPABILITIES MSR */ #define X86_FEATURE_SPEC_CTRL_SSBD (18*32+31)/* "" Speculative Store Bypass Disable */ +/* Intel-defined KeyLocker feature CPUID level 0x00000019 (EBX), word 20*/ +#define X86_FEATURE_KL_INS_ENABLED (19*32 + 0)/* "" Key Locker instructions */ +#define X86_FEATURE_KL_WIDE (19*32 + 2)/* "" Wide Key Locker instructions */ +#define X86_FEATURE_IWKEY_BACKUP (19*32 + 4)/* "" IWKey backup */ + +/* Intel-defined KeyLocker feature CPUID level 0x00000019 (ECX), word 21*/ +#define X86_FEATURE_IWKEY_NOBACKUP (20*32 + 0)/* "" NoBackup parameter to LOADIWKEY */ +#define X86_FEATURE_IWKEY_RAND (20*32 + 1)/* IWKey Randomization */ +/* * BUG word(s) */
arch/x86/include/asm/disabled-features.h +1 -1
@@ -91,6 +91,6 @@ DISABLE_ENQCMD|DISABLE_KEYLOCKER)#define DISABLED_MASK17 0#define DISABLED_MASK18 0 -#define DISABLED_MASK_CHECK BUILD_BUG_ON_ZERO(NCAPINTS != 19) +#define DISABLED_MASK_CHECK BUILD_BUG_ON_ZERO(NCAPINTS != 21)#endif /* _ASM_X86_DISABLED_FEATURES_H */
arch/x86/include/asm/required-features.h +1 -1
@@ -101,6 +101,6 @@#define REQUIRED_MASK16 0#define REQUIRED_MASK17 0#define REQUIRED_MASK18 0 -#define REQUIRED_MASK_CHECK BUILD_BUG_ON_ZERO(NCAPINTS != 19) +#define REQUIRED_MASK_CHECK BUILD_BUG_ON_ZERO(NCAPINTS != 21)#endif /* _ASM_X86_REQUIRED_FEATURES_H */
arch/x86/kernel/cpu/common.c +7 -0
@@ -995,6 +995,13 @@ void get_cpu_cap(struct cpuinfo_x86 *c) c->x86_capability[CPUID_D_1_EAX ] = eax; } +/* Additional Intel-defined KeyLocker flags: level 0x00000019 */ +if (c->cpuid_level >=0x00000019 ) { +cpuid (0x00000019 , &eax, &ebx, &ecx, &edx); + c->x86_capability[CPUID_19_EBX ] = ebx; + c->x86_capability[CPUID_19_ECX ] = ecx; + } +/* AMD-defined flags: level 0x80000001 */ eax =cpuid_eax (0x80000000 ); c->extended_cpuid_level = eax;
Signature · 1 line
1.8.3.1
Sean Christopherson
maintainerRe: [RFC PATCH 02/12] x86/cpufeature: Add CPUID.19H:{EBX,ECX} cpuid leaves
Quoted 75 lines · Robert Hoo
Though KeyLocker is generally enumerated by CPUID.(07H,0):ECX.KL[bit23], CPUID.19H:{EBX,ECX} enumerate more details of KeyLocker supporting status.
CPUID.19H:EBX
bit0 enumerates if OS (CR4.KeyLocker) and BIOS have enabled KeyLocker. bit2 enumerates if wide Key Locker instructions are supported. bit4 enumerates if IWKey backup is supported.
CPUID.19H:ECX
bit0 enumerates if the NoBackup parameter to LOADIWKEY is supported. bit1 enumerates if IWKey randomization is supported.Define these 2
cpuid_leafsso thatget_cpu_cap()will have these capabilities included, which will be the knowledge source of KVM on host KeyLocker capabilities.Most of above features don't have the necessity to appear in
/proc/cpuinfo, except "iwkey_rand", which we think might be interesting for user to easily know if his system is using randomized IWKey.Signed-off-by Robert Hoo <[email protected]>--- arch/x86/include/asm/cpufeature.h | 6 ++++-- arch/x86/include/asm/cpufeatures.h | 11 ++++++++++- arch/x86/include/asm/disabled-features.h | 2 +- arch/x86/include/asm/required-features.h | 2 +- arch/x86/kernel/cpu/common.c | 7 +++++++ 5 files changed, 23 insertions(+), 5 deletions(-)arch/x86/include/asm/cpufeature.h +4
-2@@ -30,6 +30,8 @@ enum cpuid_leafsCPUID_7_ECX ,CPUID_8000_0007_EBX ,CPUID_7_EDX , +CPUID_19_EBX , + CPUID_19_ECX, };#ifdef CONFIG_X86_FEATURE_NAMES @@ -89,7 +91,7 @@ enum cpuid_leafs CHECK_BIT_IN_MASK_WORD(REQUIRED_MASK, 17, feature_bit) || \ CHECK_BIT_IN_MASK_WORD(REQUIRED_MASK, 18, feature_bit) || \ REQUIRED_MASK_CHECK || \ - BUILD_BUG_ON_ZERO(NCAPINTS != 19)) + BUILD_BUG_ON_ZERO(NCAPINTS != 21))#define DISABLED_MASK_BIT_SET (feature_bit) \ ( CHECK_BIT_IN_MASK_WORD(DISABLED_MASK, 0, feature_bit) || \@@ -112,7 +114,7 @@ enum cpuid_leafs CHECK_BIT_IN_MASK_WORD(DISABLED_MASK, 17, feature_bit) || \ CHECK_BIT_IN_MASK_WORD(DISABLED_MASK, 18, feature_bit) || \ DISABLED_MASK_CHECK || \ - BUILD_BUG_ON_ZERO(NCAPINTS != 19)) + BUILD_BUG_ON_ZERO(NCAPINTS != 21))#define cpu_has (c, bit) \ (__builtin_constant_p(bit) && REQUIRED_MASK_BIT_SET(bit) ? 1 : \arch/x86/include/asm/cpufeatures.h +1
-1@@ -13,7 +13,7 @@/* * Defines x86 CPU feature bits */ -#define NCAPINTS 19/* N 32-bit words worth of info */ +#define NCAPINTS 21/* N 32-bit words worth of info */ #define NBUGINTS 1/* N 32-bit bug flags */ /* @@ -382,6 +382,15 @@#define X86_FEATURE_CORE_CAPABILITIES (18*32+30)/* "" IA32_CORE_CAPABILITIES MSR */
arch/x86/include/asm/cpufeatures.h line 392
Quoted 10 lines
arch/x86/include/asm/cpufeatures.h +8
-0#define X86_FEATURE_SPEC_CTRL_SSBD (18*32+31)/* "" Speculative Store Bypass Disable */ +/* Intel-defined KeyLocker feature CPUID level 0x00000019 (EBX), word 20*/ +#define X86_FEATURE_KL_INS_ENABLED (19*32 + 0)/* "" Key Locker instructions */ +#define X86_FEATURE_KL_WIDE (19*32 + 2)/* "" Wide Key Locker instructions */ +#define X86_FEATURE_IWKEY_BACKUP (19*32 + 4)/* "" IWKey backup */ + +/* Intel-defined KeyLocker feature CPUID level 0x00000019 (ECX), word 21*/ +#define X86_FEATURE_IWKEY_NOBACKUP (20*32 + 0)/* "" NoBackup parameter to LOADIWKEY */ +#define X86_FEATURE_IWKEY_RAND (20*32 + 1)/* IWKey Randomization */
These should probably go into a Linux-defined leaf, I'm guessing neither leaf will be anywhere near full, at least in Linux. KVM's reverse-CPUID code will likely/hopefully be gaining support for scattered leafs in the near future[*], that side of things should be a non-issue if/when this lands.
Re: [RFC PATCH 02/12] x86/cpufeature: Add CPUID.19H:{EBX,ECX} cpuid leaves
Quoted 46 lines · Sean Christopherson
Quoted 32 lines
arch/x86/include/asm/cpufeatures.h +0
-1@@ -13,7 +13,7 @@/* * Defines x86 CPU feature bits */ -#define NCAPINTS 19/* N 32-bit words worth of info */
+#define NCAPINTS 21 /* N 32-bit words worth
of info */
#define NBUGINTS 1 /* N 32-bit bug flags *//*
arch/x86/include/asm/cpufeatures.h +0
-0@@ -382,6 +382,15 @@#define X86_FEATURE_CORE_CAPABILITIES (18*32+30)/* ""
IA32_CORE_CAPABILITIESMSR */
#defineX86_FEATURE_SPEC_CTRL_SSBD(18*32+31) /* "" Speculative
Store Bypass Disable */+/* Intel-defined KeyLocker feature CPUID level
0x00000019(EBX), word 20*/
+#defineX86_FEATURE_KL_INS_ENABLED(19*32 + 0) /* "" Key Locker instructions */
+#defineX86_FEATURE_KL_WIDE(19*32 + 2) /* "" Wide Key Locker instructions */
+#defineX86_FEATURE_IWKEY_BACKUP(19*32 + 4) /* "" IWKey backup */arch/x86/include/asm/cpufeatures.h +2
-0+ +/* Intel-defined KeyLocker feature CPUID level 0x00000019 (ECX), Quoted 5 lines
word 21*/
+#defineX86_FEATURE_IWKEY_NOBACKUP(20*32 + 0) /* "" NoBackup parameter to LOADIWKEY */
+#defineX86_FEATURE_IWKEY_RAND(20*32 + 1) /* IWKey Randomization */These should probably go into a Linux-defined leaf, I'm guessing neither leaf
will be anywhere near full, at least in Linux. KVM's reverse-CPUID code will
likely/hopefully be gaining support for scattered leafs in the near future[*],
that side of things should be a non-issue if/when this lands.
Quoted 1 line
Yes, in my internal private tree, I have refactored code based on your patch.
BTW, I'm thinking, what if when those new HW-defined leaves got more occupied? will then they be moved from the Linux-defined leaves to new truely-map-to-HW-definition leaves?
RFC PATCH 3/12 kvm/vmx: Introduce the new tertiary processor-based VM-execution controls
In reply to Robert HooThe Tertiary Exec Control field is enabled by Primary Exec Control field's bit 17. And the Tertiary-Exec-Control-Field.bit[0] in turn controls the 'LOADIWKEY' VM-exit. Its companion VMX CTRL MSR is IA32_VMX_PROCBASED_CTLS3 (0x492). Please be noted that they're 64 bit, different from previous control fields.
--- arch/x86/include/asm/msr-index.h | 1 + arch/x86/include/asm/vmx.h | 3 +++ arch/x86/include/asm/vmxfeatures.h | 3 ++- arch/x86/kernel/cpu/feat_ctl.c | 9 +++++++++ arch/x86/kvm/vmx/capabilities.h | 7 +++++++ arch/x86/kvm/vmx/vmcs.h | 1 + arch/x86/kvm/vmx/vmx.c | 23 ++++++++++++++++++++--- arch/x86/kvm/vmx/vmx.h | 8 ++++++++ 8 files changed, 51 insertions(+), 4 deletions(-)
arch/x86/include/asm/msr-index.h +1 -0
@@ -902,6 +902,7 @@#define MSR_IA32_VMX_TRUE_EXIT_CTLS 0x0000048f#define MSR_IA32_VMX_TRUE_ENTRY_CTLS 0x00000490#define MSR_IA32_VMX_VMFUNC 0x00000491 +#define MSR_IA32_VMX_PROCBASED_CTLS3 0x00000492/* VMX_BASIC bits and bitmasks */ #define VMX_BASIC_VMCS_SIZE_SHIFT 32
arch/x86/include/asm/vmx.h +3 -0
@@ -31,6 +31,7 @@#define CPU_BASED_RDTSC_EXITING VMCS_CONTROL_BIT(RDTSC_EXITING)#define CPU_BASED_CR3_LOAD_EXITING VMCS_CONTROL_BIT(CR3_LOAD_EXITING)#define CPU_BASED_CR3_STORE_EXITING VMCS_CONTROL_BIT(CR3_STORE_EXITING) +#define CPU_BASED_ACTIVATE_TERTIARY_CONTROLS VMCS_CONTROL_BIT(TER_CONTROLS)#define CPU_BASED_CR8_LOAD_EXITING VMCS_CONTROL_BIT(CR8_LOAD_EXITING)#define CPU_BASED_CR8_STORE_EXITING VMCS_CONTROL_BIT(CR8_STORE_EXITING)#define CPU_BASED_TPR_SHADOW VMCS_CONTROL_BIT(VIRTUAL_TPR)
@@ -219,6 +220,8 @@ enum vmcs_field {ENCLS_EXITING_BITMAP_HIGH =0x0000202F ,TSC_MULTIPLIER =0x00002032 ,TSC_MULTIPLIER_HIGH =0x00002033 , +TERTIARY_VM_EXEC_CONTROL =0x00002034 , +TERTIARY_VM_EXEC_CONTROL_HIGH =0x00002035 ,GUEST_PHYSICAL_ADDRESS =0x00002400 ,GUEST_PHYSICAL_ADDRESS_HIGH =0x00002401 , VMCS_LINK_POINTER = 0x00002800,
arch/x86/include/asm/vmxfeatures.h +2 -1
@@ -5,7 +5,7 @@/* * Defines VMX CPU feature bits */ -#define NVMXINTS 3/* N 32-bit words worth of info */ +#define NVMXINTS 5/* N 32-bit words worth of info */ /* * Note: If the comment begins with a quoted string, that string is used
@@ -43,6 +43,7 @@#define VMX_FEATURE_RDTSC_EXITING ( 1*32+ 12)/* "" VM-Exit on RDTSC */ #define VMX_FEATURE_CR3_LOAD_EXITING ( 1*32+ 15)/* "" VM-Exit on writes to CR3 */ #define VMX_FEATURE_CR3_STORE_EXITING ( 1*32+ 16)/* "" VM-Exit on reads from CR3 */ +#define VMX_FEATURE_TER_CONTROLS (1*32 + 17)/* "" Enable Tertiary VM-Execution Controls */ #define VMX_FEATURE_CR8_LOAD_EXITING ( 1*32+ 19)/* "" VM-Exit on writes to CR8 */ #define VMX_FEATURE_CR8_STORE_EXITING ( 1*32+ 20)/* "" VM-Exit on reads from CR8 */ #define VMX_FEATURE_VIRTUAL_TPR ( 1*32+ 21)/* "vtpr" TPR virtualization, a.k.a. TPR shadow */
arch/x86/kernel/cpu/feat_ctl.c +9 -0
@@ -15,6 +15,8 @@ enum vmx_feature_leafs {MISC_FEATURES =0 ,PRIMARY_CTLS ,SECONDARY_CTLS , +TERTIARY_CTLS_LOW , +TERTIARY_CTLS_HIGH , NR_VMX_FEATURE_WORDS, };
@@ -42,6 +44,13 @@ static void init_vmx_capabilities(struct cpuinfo_x86 *c)rdmsr_safe (MSR_IA32_VMX_PROCBASED_CTLS2 , &ign, &supported); c->vmx_capability[SECONDARY_CTLS ] = supported; +/* +* For tertiary execution controls MSR, it's actually a 64bit allowed-1. +*/ +rdmsr_safe (MSR_IA32_VMX_PROCBASED_CTLS3 , &ign, &supported); + c->vmx_capability[TERTIARY_CTLS_LOW ] = ign; + c->vmx_capability[TERTIARY_CTLS_HIGH ] = supported; +rdmsr (MSR_IA32_VMX_PINBASED_CTLS , ign, supported);rdmsr_safe (MSR_IA32_VMX_VMFUNC , &ign, &funcs);
arch/x86/kvm/vmx/capabilities.h +7 -0
@@ -57,6 +57,7 @@ struct vmcs_config {u32 pin_based_exec_ctrl;u32 cpu_based_exec_ctrl;u32 cpu_based_2nd_exec_ctrl; +u64 cpu_based_3rd_exec_ctrl;u32 vmexit_ctrl;u32 vmentry_ctrl;struct nested_vmx_msrs nested;
@@ -130,6 +131,12 @@ static inline bool cpu_has_secondary_exec_ctrls(void)CPU_BASED_ACTIVATE_SECONDARY_CONTROLS ; } +static inline bool cpu_has_tertiary_exec_ctrls (void ) +{ +return vmcs_config.cpu_based_exec_ctrl & +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ; +} +static inline bool cpu_has_vmx_virtualize_apic_accesses (void ) { return vmcs_config.cpu_based_2nd_exec_ctrl &
arch/x86/kvm/vmx/vmcs.h +1 -0
@@ -48,6 +48,7 @@ struct vmcs_controls_shadow {u32 pin;u32 exec;u32 secondary_exec; +u64 tertiary_exec; };/*
arch/x86/kvm/vmx/vmx.c +20 -3
@@ -2376,6 +2376,7 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf,u32 _pin_based_exec_control =0 ;u32 _cpu_based_exec_control =0 ;u32 _cpu_based_2nd_exec_control =0 ; +u64 _cpu_based_3rd_exec_control =0 ;u32 _vmexit_control =0 ;u32 _vmentry_control =0 ;
@@ -2397,7 +2398,8 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf, opt =CPU_BASED_TPR_SHADOW |CPU_BASED_USE_MSR_BITMAPS | -CPU_BASED_ACTIVATE_SECONDARY_CONTROLS ; +CPU_BASED_ACTIVATE_SECONDARY_CONTROLS | +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ;if (adjust_vmx_controls (min, opt,MSR_IA32_VMX_PROCBASED_CTLS , &_cpu_based_exec_control) <0 )return -EIO ;
@@ -2557,6 +2559,7 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf, vmcs_conf->pin_based_exec_ctrl = _pin_based_exec_control; vmcs_conf->cpu_based_exec_ctrl = _cpu_based_exec_control; vmcs_conf->cpu_based_2nd_exec_ctrl = _cpu_based_2nd_exec_control; + vmcs_conf->cpu_based_3rd_exec_ctrl = _cpu_based_3rd_exec_control; vmcs_conf->vmexit_ctrl = _vmexit_control; vmcs_conf->vmentry_ctrl = _vmentry_control;
@@ -4200,6 +4203,12 @@ u32 vmx_exec_control(struct vcpu_vmx *vmx)#define vmx_adjust_sec_exec_exiting (vmx, exec_control, lname, uname) \ vmx_adjust_sec_exec_control(vmx, exec_control, lname, uname, uname##_EXITING, true) +static u64 vmx_tertiary_exec_control (struct vcpu_vmx *vmx) +{ +/* Though currently, no special adjustment. There might be in the future*/ +return vmcs_config.cpu_based_3rd_exec_ctrl; +} +static void vmx_compute_secondary_exec_control (struct vcpu_vmx *vmx) {struct kvm_vcpu *vcpu = &vmx->vcpu;
@@ -4310,6 +4319,9 @@ static void init_vmcs(struct vcpu_vmx *vmx)secondary_exec_controls_set (vmx, vmx->secondary_exec_control); } +if (cpu_has_tertiary_exec_ctrls ()) +tertiary_exec_controls_set (vmx,vmx_tertiary_exec_control (vmx)); +if (kvm_vcpu_apicv_active (&vmx->vcpu)) {vmcs_write64 (EOI_EXIT_BITMAP0 ,0 );vmcs_write64 (EOI_EXIT_BITMAP1 ,0 );
@@ -5778,6 +5790,7 @@ void dump_vmcs(void) {u32 vmentry_ctl, vmexit_ctl;u32 cpu_based_exec_ctrl, pin_based_exec_ctrl, secondary_exec_control; +u64 tertiary_exec_control =0 ;unsigned long cr4;u64 efer;
@@ -5796,6 +5809,9 @@ void dump_vmcs(void)if (cpu_has_secondary_exec_ctrls ()) secondary_exec_control =vmcs_read32 (SECONDARY_VM_EXEC_CONTROL ); +if (cpu_has_tertiary_exec_ctrls ()) + tertiary_exec_control =vmcs_read64 (TERTIARY_VM_EXEC_CONTROL ); +pr_err ("*** Guest State ***\n" ); pr_err("CR0: actual=0x%016lx, shadow=0x%016lx, gh_mask=%016lx\n", vmcs_readl(GUEST_CR0), vmcs_readl(CR0_READ_SHADOW),
@@ -5878,8 +5894,9 @@ void dump_vmcs(void) vmcs_read64(HOST_IA32_PERF_GLOBAL_CTRL));pr_err ("*** Control State ***\n" ); -pr_err ("PinBased=%08x CPUBased=%08x SecondaryExec=%08x\n" , - pin_based_exec_ctrl, cpu_based_exec_ctrl, secondary_exec_control); +pr_err ("PinBased=0x%08x CPUBased=0x%08x SecondaryExec=0x%08x TertiaryExec=0x%016llx\n" , + pin_based_exec_ctrl, cpu_based_exec_ctrl, secondary_exec_control, + tertiary_exec_control);pr_err ("EntryControls=%08x ExitControls=%08x\n" , vmentry_ctl, vmexit_ctl); pr_err("ExceptionBitmap=%08x PFECmask=%08x PFECmatch=%08x\n", vmcs_read32(EXCEPTION_BITMAP),
arch/x86/kvm/vmx/vmx.h +8 -0
@@ -373,6 +373,14 @@ static inline u8 vmx_get_rvi(void) BUILD_CONTROLS_SHADOW(exec, CPU_BASED_VM_EXEC_CONTROL) BUILD_CONTROLS_SHADOW(secondary_exec, SECONDARY_VM_EXEC_CONTROL) +static inline void tertiary_exec_controls_set (struct vcpu_vmx *vmx,u64 val) +{ +if (vmx->loaded_vmcs->controls_shadow.tertiary_exec != val) { +vmcs_write64 (TERTIARY_VM_EXEC_CONTROL , val); + vmx->loaded_vmcs->controls_shadow.tertiary_exec = val; + } +} +static inline void vmx_register_cache_reset (struct kvm_vcpu *vcpu) { vcpu->arch.regs_avail = ~((1 << VCPU_REGS_RIP) | (1 << VCPU_REGS_RSP)
Signature · 1 line
1.8.3.1
Re: [RFC PATCH 03/12] kvm/vmx: Introduce the new tertiary processor-based VM-execution controls
Quoted 198 lines · Robert Hoo
The Tertiary Exec Control field is enabled by Primary Exec Control field's bit 17. And the Tertiary-Exec-Control-Field.bit[0] in turn controls the 'LOADIWKEY' VM-exit. Its companion VMX CTRL MSR is
IA32_VMX_PROCBASED_CTLS3(0x492). Please be noted that they're 64 bit, different from previous control fields.Signed-off-by Robert Hoo <[email protected]>--- arch/x86/include/asm/msr-index.h | 1 + arch/x86/include/asm/vmx.h | 3 +++ arch/x86/include/asm/vmxfeatures.h | 3 ++- arch/x86/kernel/cpu/feat_ctl.c | 9 +++++++++ arch/x86/kvm/vmx/capabilities.h | 7 +++++++ arch/x86/kvm/vmx/vmcs.h | 1 + arch/x86/kvm/vmx/vmx.c | 23 ++++++++++++++++++++--- arch/x86/kvm/vmx/vmx.h | 8 ++++++++ 8 files changed, 51 insertions(+), 4 deletions(-)arch/x86/include/asm/msr-index.h +1
-0@@ -902,6 +902,7 @@#define MSR_IA32_VMX_TRUE_EXIT_CTLS 0x0000048f#define MSR_IA32_VMX_TRUE_ENTRY_CTLS 0x00000490#define MSR_IA32_VMX_VMFUNC 0x00000491 +#define MSR_IA32_VMX_PROCBASED_CTLS3 0x00000492/* VMX_BASIC bits and bitmasks */ #define VMX_BASIC_VMCS_SIZE_SHIFT 32arch/x86/include/asm/vmx.h +3
-0@@ -31,6 +31,7 @@#define CPU_BASED_RDTSC_EXITING VMCS_CONTROL_BIT(RDTSC_EXITING)#define CPU_BASED_CR3_LOAD_EXITING VMCS_CONTROL_BIT(CR3_LOAD_EXITING)#define CPU_BASED_CR3_STORE_EXITING VMCS_CONTROL_BIT(CR3_STORE_EXITING) +#define CPU_BASED_ACTIVATE_TERTIARY_CONTROLS VMCS_CONTROL_BIT(TER_CONTROLS)#define CPU_BASED_CR8_LOAD_EXITING VMCS_CONTROL_BIT(CR8_LOAD_EXITING)#define CPU_BASED_CR8_STORE_EXITING VMCS_CONTROL_BIT(CR8_STORE_EXITING)#define CPU_BASED_TPR_SHADOW VMCS_CONTROL_BIT(VIRTUAL_TPR)@@ -219,6 +220,8 @@ enum vmcs_field {ENCLS_EXITING_BITMAP_HIGH =0x0000202F ,TSC_MULTIPLIER =0x00002032 ,TSC_MULTIPLIER_HIGH =0x00002033 , +TERTIARY_VM_EXEC_CONTROL =0x00002034 , +TERTIARY_VM_EXEC_CONTROL_HIGH =0x00002035 ,GUEST_PHYSICAL_ADDRESS =0x00002400 ,GUEST_PHYSICAL_ADDRESS_HIGH =0x00002401 , VMCS_LINK_POINTER = 0x00002800,arch/x86/include/asm/vmxfeatures.h +2
-1@@ -5,7 +5,7 @@/* * Defines VMX CPU feature bits */ -#define NVMXINTS 3/* N 32-bit words worth of info */ +#define NVMXINTS 5/* N 32-bit words worth of info */ /* * Note: If the comment begins with a quoted string, that string is used @@ -43,6 +43,7 @@#define VMX_FEATURE_RDTSC_EXITING ( 1*32+ 12)/* "" VM-Exit on RDTSC */ #define VMX_FEATURE_CR3_LOAD_EXITING ( 1*32+ 15)/* "" VM-Exit on writes to CR3 */ #define VMX_FEATURE_CR3_STORE_EXITING ( 1*32+ 16)/* "" VM-Exit on reads from CR3 */ +#define VMX_FEATURE_TER_CONTROLS (1*32 + 17)/* "" Enable Tertiary VM-Execution Controls */ #define VMX_FEATURE_CR8_LOAD_EXITING ( 1*32+ 19)/* "" VM-Exit on writes to CR8 */ #define VMX_FEATURE_CR8_STORE_EXITING ( 1*32+ 20)/* "" VM-Exit on reads from CR8 */ #define VMX_FEATURE_VIRTUAL_TPR ( 1*32+ 21)/* "vtpr" TPR virtualization, a.k.a. TPR shadow */ arch/x86/kernel/cpu/feat_ctl.c +9
-0@@ -15,6 +15,8 @@ enum vmx_feature_leafs {MISC_FEATURES =0 ,PRIMARY_CTLS ,SECONDARY_CTLS , +TERTIARY_CTLS_LOW , +TERTIARY_CTLS_HIGH , NR_VMX_FEATURE_WORDS, };@@ -42,6 +44,13 @@ static void init_vmx_capabilities(struct cpuinfo_x86 *c)rdmsr_safe (MSR_IA32_VMX_PROCBASED_CTLS2 , &ign, &supported); c->vmx_capability[SECONDARY_CTLS ] = supported; +/* +* For tertiary execution controls MSR, it's actually a 64bit allowed-1. +*/ +rdmsr_safe (MSR_IA32_VMX_PROCBASED_CTLS3 , &ign, &supported); + c->vmx_capability[TERTIARY_CTLS_LOW ] = ign; + c->vmx_capability[TERTIARY_CTLS_HIGH ] = supported; +rdmsr (MSR_IA32_VMX_PINBASED_CTLS , ign, supported);rdmsr_safe (MSR_IA32_VMX_VMFUNC , &ign, &funcs);arch/x86/kvm/vmx/capabilities.h +7
-0@@ -57,6 +57,7 @@ struct vmcs_config {u32 pin_based_exec_ctrl;u32 cpu_based_exec_ctrl;u32 cpu_based_2nd_exec_ctrl; +u64 cpu_based_3rd_exec_ctrl;u32 vmexit_ctrl;u32 vmentry_ctrl;struct nested_vmx_msrs nested;@@ -130,6 +131,12 @@ static inline bool cpu_has_secondary_exec_ctrls(void)CPU_BASED_ACTIVATE_SECONDARY_CONTROLS ; } +static inline bool cpu_has_tertiary_exec_ctrls (void ) +{ +return vmcs_config.cpu_based_exec_ctrl & +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ; +} +static inline bool cpu_has_vmx_virtualize_apic_accesses (void ) { return vmcs_config.cpu_based_2nd_exec_ctrl &arch/x86/kvm/vmx/vmcs.h +1
-0@@ -48,6 +48,7 @@ struct vmcs_controls_shadow {u32 pin;u32 exec;u32 secondary_exec; +u64 tertiary_exec; };/* arch/x86/kvm/vmx/vmx.c +14
-1@@ -2376,6 +2376,7 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf,u32 _pin_based_exec_control =0 ;u32 _cpu_based_exec_control =0 ;u32 _cpu_based_2nd_exec_control =0 ; +u64 _cpu_based_3rd_exec_control =0 ;u32 _vmexit_control =0 ;u32 _vmentry_control =0 ;@@ -2397,7 +2398,8 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf, opt =CPU_BASED_TPR_SHADOW |CPU_BASED_USE_MSR_BITMAPS | -CPU_BASED_ACTIVATE_SECONDARY_CONTROLS ; +CPU_BASED_ACTIVATE_SECONDARY_CONTROLS | +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ;if (adjust_vmx_controls (min, opt,MSR_IA32_VMX_PROCBASED_CTLS , &_cpu_based_exec_control) <0 )return -EIO ;@@ -2557,6 +2559,7 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf, vmcs_conf->pin_based_exec_ctrl = _pin_based_exec_control; vmcs_conf->cpu_based_exec_ctrl = _cpu_based_exec_control; vmcs_conf->cpu_based_2nd_exec_ctrl = _cpu_based_2nd_exec_control; + vmcs_conf->cpu_based_3rd_exec_ctrl = _cpu_based_3rd_exec_control; vmcs_conf->vmexit_ctrl = _vmexit_control; vmcs_conf->vmentry_ctrl = _vmentry_control;@@ -4200,6 +4203,12 @@ u32 vmx_exec_control(struct vcpu_vmx *vmx)#define vmx_adjust_sec_exec_exiting (vmx, exec_control, lname, uname) \ vmx_adjust_sec_exec_control(vmx, exec_control, lname, uname, uname##_EXITING, true) +static u64 vmx_tertiary_exec_control (struct vcpu_vmx *vmx) +{ +/* Though currently, no special adjustment. There might be in the future*/ +return vmcs_config.cpu_based_3rd_exec_ctrl; +} +static void vmx_compute_secondary_exec_control (struct vcpu_vmx *vmx) {struct kvm_vcpu *vcpu = &vmx->vcpu;@@ -4310,6 +4319,9 @@ static void init_vmcs(struct vcpu_vmx *vmx)secondary_exec_controls_set (vmx, vmx->secondary_exec_control); } +if (cpu_has_tertiary_exec_ctrls ()) +tertiary_exec_controls_set (vmx,vmx_tertiary_exec_control (vmx)); +if (kvm_vcpu_apicv_active (&vmx->vcpu)) {vmcs_write64 (EOI_EXIT_BITMAP0 ,0 );vmcs_write64 (EOI_EXIT_BITMAP1 ,0 );@@ -5778,6 +5790,7 @@ void dump_vmcs(void) {u32 vmentry_ctl, vmexit_ctl;u32 cpu_based_exec_ctrl, pin_based_exec_ctrl, secondary_exec_control; +u64 tertiary_exec_control =0 ;unsigned long cr4;u64 efer;
arch/x86/kvm/vmx/vmx.c void dump_vmcs(void) · line 5813
Quoted 5 lines
arch/x86/kvm/vmx/vmx.c +2
-0@@ -5796,6 +5809,9 @@ void dump_vmcs(void)if (cpu_has_secondary_exec_ctrls ()) secondary_exec_control =vmcs_read32 (SECONDARY_VM_EXEC_CONTROL ); +if (cpu_has_tertiary_exec_ctrls ()) + tertiary_exec_control =vmcs_read64 (TERTIARY_VM_EXEC_CONTROL );
We'll have to do something about Enlightened VMCS I believe. In theory, when eVMCS is in use, 'CPU_BASED_ACTIVATE_TERTIARY_CONTROLS' should not be exposed, e.g. when KVM hosts a EVMCS enabled guest the control should be filtered out. Something like (completely untested):
arch/x86/kvm/vmx/evmcs.c +1 -0
@@ -299,6 +299,7 @@ const unsigned int nr_evmcs_1_fields = ARRAY_SIZE(vmcs_field_to_evmcs_1);__init void evmcs_sanitize_exec_ctrls (struct vmcs_config *vmcs_conf) { + vmcs_conf->cpu_based_exec_ctrl &= ~EVMCS1_UNSUPPORTED_EXEC_CTRL ; vmcs_conf->pin_based_exec_ctrl &= ~EVMCS1_UNSUPPORTED_PINCTRL ; vmcs_conf->cpu_based_2nd_exec_ctrl &= ~EVMCS1_UNSUPPORTED_2NDEXEC ;
arch/x86/kvm/vmx/evmcs.h +1 -0
@@ -50,6 +50,7 @@ DECLARE_STATIC_KEY_FALSE(enable_evmcs);*/ #define EVMCS1_UNSUPPORTED_PINCTRL (PIN_BASED_POSTED_INTR | \ PIN_BASED_VMX_PREEMPTION_TIMER) +#define EVMCS1_UNSUPPORTED_EXEC_CTRL (CPU_BASED_ACTIVATE_TERTIARY_CONTROLS)#define EVMCS1_UNSUPPORTED_2NDEXEC \ (SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY | \ SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES | \
should do the job I think.
Quoted 35 lines
arch/x86/kvm/vmx/vmx.c +4
-2+pr_err ("*** Guest State ***\n" ); pr_err("CR0: actual=0x%016lx, shadow=0x%016lx, gh_mask=%016lx\n", vmcs_readl(GUEST_CR0), vmcs_readl(CR0_READ_SHADOW),@@ -5878,8 +5894,9 @@ void dump_vmcs(void) vmcs_read64(HOST_IA32_PERF_GLOBAL_CTRL));pr_err ("*** Control State ***\n" ); -pr_err ("PinBased=%08x CPUBased=%08x SecondaryExec=%08x\n" , - pin_based_exec_ctrl, cpu_based_exec_ctrl, secondary_exec_control); +pr_err ("PinBased=0x%08x CPUBased=0x%08x SecondaryExec=0x%08x TertiaryExec=0x%016llx\n" , + pin_based_exec_ctrl, cpu_based_exec_ctrl, secondary_exec_control, + tertiary_exec_control);pr_err ("EntryControls=%08x ExitControls=%08x\n" , vmentry_ctl, vmexit_ctl); pr_err("ExceptionBitmap=%08x PFECmask=%08x PFECmatch=%08x\n", vmcs_read32(EXCEPTION_BITMAP),arch/x86/kvm/vmx/vmx.h +8
-0@@ -373,6 +373,14 @@ static inline u8 vmx_get_rvi(void) BUILD_CONTROLS_SHADOW(exec, CPU_BASED_VM_EXEC_CONTROL) BUILD_CONTROLS_SHADOW(secondary_exec, SECONDARY_VM_EXEC_CONTROL) +static inline void tertiary_exec_controls_set (struct vcpu_vmx *vmx,u64 val) +{ +if (vmx->loaded_vmcs->controls_shadow.tertiary_exec != val) { +vmcs_write64 (TERTIARY_VM_EXEC_CONTROL , val); + vmx->loaded_vmcs->controls_shadow.tertiary_exec = val; + } +} +static inline void vmx_register_cache_reset (struct kvm_vcpu *vcpu) { vcpu->arch.regs_avail = ~((1 << VCPU_REGS_RIP) | (1 << VCPU_REGS_RSP)
Signature · 1 line
Vitaly
Re: [RFC PATCH 03/12] kvm/vmx: Introduce the new tertiary processor-based VM-execution controls
Quoted 2 lines · Vitaly Kuznetsov
Robert Hoo <[email protected]> writes:
[...]
Quoted 125 lines
Quoted 76 lines
/*
arch/x86/kvm/vmx/vmx.c +3
-1@@ -2376,6 +2376,7 @@ static __init int setup_vmcs_config(structvmcs_config *vmcs_conf, u32 _pin_based_exec_control = 0;u32 _cpu_based_exec_control =0 ;u32 _cpu_based_2nd_exec_control =0 ; +u64 _cpu_based_3rd_exec_control =0 ;u32 _vmexit_control =0 ;u32 _vmentry_control =0 ;@@ -2397,7 +2398,8 @@ static __init int setup_vmcs_config(structvmcs_config *vmcs_conf, opt =CPU_BASED_TPR_SHADOW |CPU_BASED_USE_MSR_BITMAPS | -CPU_BASED_ACTIVATE_SECONDARY_CONTROLS ; +CPU_BASED_ACTIVATE_SECONDARY_CONTROLS | +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ;if (adjust_vmx_controls (min, opt,MSR_IA32_VMX_PROCBASED_CTLS , &_cpu_based_exec_control) <0 )arch/x86/kvm/vmx/vmx.c +1
-0return -EIO ;@@ -2557,6 +2559,7 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf, vmcs_conf->pin_based_exec_ctrl = _pin_based_exec_control; vmcs_conf->cpu_based_exec_ctrl = _cpu_based_exec_control; vmcs_conf->cpu_based_2nd_exec_ctrl = _cpu_based_2nd_exec_control; + vmcs_conf->cpu_based_3rd_exec_ctrl = _cpu_based_3rd_exec_control;arch/x86/kvm/vmx/vmx.c +3
-0vmcs_conf->vmexit_ctrl = _vmexit_control; vmcs_conf->vmentry_ctrl = _vmentry_control;@@ -4200,6 +4203,12 @@ u32 vmx_exec_control(struct vcpu_vmx *vmx)#define vmx_adjust_sec_exec_exiting (vmx, exec_control, lname, uname) \ vmx_adjust_sec_exec_control(vmx, exec_control, lname, uname, uname##_EXITING, true) +static u64 vmx_tertiary_exec_control (struct vcpu_vmx *vmx) +{ +/* Though currently, no special adjustment. There might be in the future*/
arch/x86/kvm/vmx/vmx.c +3
-0+return vmcs_config.cpu_based_3rd_exec_ctrl; +} + static void vmx_compute_secondary_exec_control(struct vcpu_vmx*vmx)
{arch/x86/kvm/vmx/vmx.c +3
-0struct kvm_vcpu *vcpu = &vmx->vcpu;@@ -4310,6 +4319,9 @@ static void init_vmcs(struct vcpu_vmx *vmx)secondary_exec_controls_set (vmx, vmx- >secondary_exec_control); } +if (cpu_has_tertiary_exec_ctrls ()) +tertiary_exec_controls_set (vmx,vmx_tertiary_exec_control (vmx)); +if (kvm_vcpu_apicv_active (&vmx->vcpu)) {arch/x86/kvm/vmx/vmx.c +1
-0vmcs_write64 (EOI_EXIT_BITMAP0 ,0 );vmcs_write64 (EOI_EXIT_BITMAP1 ,0 );@@ -5778,6 +5790,7 @@ void dump_vmcs(void) {u32 vmentry_ctl, vmexit_ctl;u32 cpu_based_exec_ctrl, pin_based_exec_ctrl, secondary_exec_control; +u64 tertiary_exec_control =0 ;unsigned long cr4;u64 efer;arch/x86/kvm/vmx/vmx.c void dump_vmcs(void) · line 5815
Quoted 7 lines
arch/x86/kvm/vmx/vmx.c +2
-0@@ -5796,6 +5809,9 @@ void dump_vmcs(void)if (cpu_has_secondary_exec_ctrls ()) secondary_exec_control =vmcs_read32 (SECONDARY_VM_EXEC_CONTROL ); +if (cpu_has_tertiary_exec_ctrls ()) + tertiary_exec_control =vmcs_read64 (TERTIARY_VM_EXEC_CONTROL );We'll have to do something about Enlightened VMCS I believe. In theory,
when eVMCS is in use, 'CPU_BASED_ACTIVATE_TERTIARY_CONTROLS' should not
be exposed, e.g. when KVM hosts a EVMCS enabled guest the control should
be filtered out. Something like (completely untested):arch/x86/kvm/vmx/evmcs.c +1
-0@@ -299,6 +299,7 @@ const unsigned int nr_evmcs_1_fields =ARRAY_SIZE (vmcs_field_to_evmcs_1);__init void evmcs_sanitize_exec_ctrls (struct vmcs_config *vmcs_conf) { + vmcs_conf->cpu_based_exec_ctrl &= ~EVMCS1_UNSUPPORTED_EXEC_CTRL ; vmcs_conf->pin_based_exec_ctrl &=~EVMCS1_UNSUPPORTED_PINCTRL; vmcs_conf->cpu_based_2nd_exec_ctrl &=~EVMCS1_UNSUPPORTED_2NDEXEC;
arch/x86/kvm/vmx/evmcs.h +1
-0@@ -50,6 +50,7 @@ DECLARE_STATIC_KEY_FALSE(enable_evmcs);*/ #define EVMCS1_UNSUPPORTED_PINCTRL (PIN_BASED_POSTED_INTR | \ PIN_BASED_VMX_PREEMPTION_TIMER) +#define EVMCS1_UNSUPPORTED_EXEC_CTRL (CPU_BASED_ACTIVATE_TERTIARY_CONTROLS)#define EVMCS1_UNSUPPORTED_2NDEXEC \(
SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY
| \
SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES
| \
Quoted 1 line
should do the job I think.
Agree, until L0 HyperV supports the new tertiary control, L1 KVM shall not expose it to its guests. Thanks Vitaly pointing out, and with detailed explanation.
BTW, when would enlightened VMCS support VMCS Tertiary Control and Key Locker feature?
Quoted 45 lines
Quoted 43 lines
arch/x86/kvm/vmx/vmx.c +1
-0+pr_err ("*** Guest State ***\n" );pr_err("CR0: actual=0x%016lx, shadow=0x%016lx,
gh_mask=%016lx\n",arch/x86/kvm/vmx/vmx.c +3
-2vmcs_readl(GUEST_CR0), vmcs_readl(CR0_READ_SHADOW),@@ -5878,8 +5894,9 @@ void dump_vmcs(void) vmcs_read64(HOST_IA32_PERF_GLOBAL_CTRL));pr_err ("*** Control State ***\n" ); -pr_err ("PinBased=%08x CPUBased=%08x SecondaryExec=%08x\n" , - pin_based_exec_ctrl, cpu_based_exec_ctrl, secondary_exec_control); + pr_err("PinBased=0x%08x CPUBased=0x%08x SecondaryExec=0x%08x TertiaryExec=0x%016llx\n", + pin_based_exec_ctrl, cpu_based_exec_ctrl, secondary_exec_control, + tertiary_exec_control);pr_err("EntryControls=%08x ExitControls=%08x\n",
vmentry_ctl,vmexit_ctl);arch/x86/kvm/vmx/vmx.c +0
-0pr_err("ExceptionBitmap=%08x PFECmask=%08x PFECmatch=%08x\n", vmcs_read32(EXCEPTION_BITMAP),arch/x86/kvm/vmx/vmx.h +8
-0@@ -373,6 +373,14 @@ static inline u8 vmx_get_rvi(void) BUILD_CONTROLS_SHADOW(exec, CPU_BASED_VM_EXEC_CONTROL) BUILD_CONTROLS_SHADOW(secondary_exec, SECONDARY_VM_EXEC_CONTROL) +static inline void tertiary_exec_controls_set (struct vcpu_vmx *vmx,u64 val) +{ +if (vmx->loaded_vmcs->controls_shadow.tertiary_exec != val) { +vmcs_write64 (TERTIARY_VM_EXEC_CONTROL , val); + vmx->loaded_vmcs->controls_shadow.tertiary_exec = val; + } +} +static inline void vmx_register_cache_reset (struct kvm_vcpu *vcpu) {
vcpu->arch.regs_avail= ~((1 <<VCPU_REGS_RIP) | (1 <<VCPU_REGS_RSP)
Re: [RFC PATCH 03/12] kvm/vmx: Introduce the new tertiary processor-based VM-execution controls
In reply to Vitaly KuznetsovQuoted 42 lines · Vitaly Kuznetsov
Robert Hoo <[email protected]> writes:
We'll have to do something about Enlightened VMCS I believe. In theory,
when eVMCS is in use, 'CPU_BASED_ACTIVATE_TERTIARY_CONTROLS' should not
be exposed, e.g. when KVM hosts a EVMCS enabled guest the control should
be filtered out. Something like (completely untested):arch/x86/kvm/vmx/evmcs.c +1
-0@@ -299,6 +299,7 @@ const unsigned int nr_evmcs_1_fields =ARRAY_SIZE (vmcs_field_to_evmcs_1);__init void evmcs_sanitize_exec_ctrls (struct vmcs_config *vmcs_conf) { + vmcs_conf->cpu_based_exec_ctrl &= ~EVMCS1_UNSUPPORTED_EXEC_CTRL ; vmcs_conf->pin_based_exec_ctrl &=~EVMCS1_UNSUPPORTED_PINCTRL; vmcs_conf->cpu_based_2nd_exec_ctrl &=~EVMCS1_UNSUPPORTED_2NDEXEC;
arch/x86/kvm/vmx/evmcs.h +1
-0@@ -50,6 +50,7 @@ DECLARE_STATIC_KEY_FALSE(enable_evmcs);*/ #define EVMCS1_UNSUPPORTED_PINCTRL (PIN_BASED_POSTED_INTR | \ PIN_BASED_VMX_PREEMPTION_TIMER) +#define EVMCS1_UNSUPPORTED_EXEC_CTRL (CPU_BASED_ACTIVATE_TERTIARY_CONTROLS)#define EVMCS1_UNSUPPORTED_2NDEXEC \(
SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY
| \
SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES
| \
Quoted 2 lines
should do the job I think.
Hi Vitaly,
I'm going to incorporate above patch in my next version. Shall I have it your signed-off-by?
Re: [RFC PATCH 03/12] kvm/vmx: Introduce the new tertiary processor-based VM-execution controls
Quoted 43 lines · Robert Hoo
Quoted 42 lines · Vitaly Kuznetsov
Robert Hoo <[email protected]> writes:
We'll have to do something about Enlightened VMCS I believe. In theory,
when eVMCS is in use, 'CPU_BASED_ACTIVATE_TERTIARY_CONTROLS' should not
be exposed, e.g. when KVM hosts a EVMCS enabled guest the control should
be filtered out. Something like (completely untested):arch/x86/kvm/vmx/evmcs.c +1
-0@@ -299,6 +299,7 @@ const unsigned int nr_evmcs_1_fields =ARRAY_SIZE (vmcs_field_to_evmcs_1);__init void evmcs_sanitize_exec_ctrls (struct vmcs_config *vmcs_conf) { + vmcs_conf->cpu_based_exec_ctrl &= ~EVMCS1_UNSUPPORTED_EXEC_CTRL ; vmcs_conf->pin_based_exec_ctrl &=~EVMCS1_UNSUPPORTED_PINCTRL; vmcs_conf->cpu_based_2nd_exec_ctrl &=~EVMCS1_UNSUPPORTED_2NDEXEC;
arch/x86/kvm/vmx/evmcs.h +1
-0@@ -50,6 +50,7 @@ DECLARE_STATIC_KEY_FALSE(enable_evmcs);*/ #define EVMCS1_UNSUPPORTED_PINCTRL (PIN_BASED_POSTED_INTR | \ PIN_BASED_VMX_PREEMPTION_TIMER) +#define EVMCS1_UNSUPPORTED_EXEC_CTRL (CPU_BASED_ACTIVATE_TERTIARY_CONTROLS)#define EVMCS1_UNSUPPORTED_2NDEXEC \(
SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY
| \
SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES
| \
Quoted 8 lines
Quoted 2 lines
should do the job I think.
Hi Vitaly,
I'm going to incorporate above patch in my next version. Shall I have it your signed-off-by?
[setup_vmcs_config: filter out tertiary control when using eVMCS]Signed-off-by Vitaly Kuznetsov <[email protected]>
You can just incorporate it into your patch or, in case you want to have it separate, feel free just add a 'Suggested-by: Vitaly Kuznetsov <[email protected]>' tag.
Thanks!
Signature · 1 line
Vitaly
Sean Christopherson
maintainerRe: [RFC PATCH 03/12] kvm/vmx: Introduce the new tertiary processor-based VM-execution controls
In reply to Robert HooQuoted 5 lines · Robert Hoo
arch/x86/kvm/vmx/vmx.h +0
-0
arch/x86/kvm/vmx/vmx.h static inline u8 vmx_get_rvi(void) · line 382
Quoted 10 lines
arch/x86/kvm/vmx/vmx.h +7
-0@@ -373,6 +373,14 @@ static inline u8 vmx_get_rvi(void) BUILD_CONTROLS_SHADOW(exec, CPU_BASED_VM_EXEC_CONTROL) BUILD_CONTROLS_SHADOW(secondary_exec, SECONDARY_VM_EXEC_CONTROL) +static inline void tertiary_exec_controls_set (struct vcpu_vmx *vmx,u64 val) +{ +if (vmx->loaded_vmcs->controls_shadow.tertiary_exec != val) { +vmcs_write64 (TERTIARY_VM_EXEC_CONTROL , val); + vmx->loaded_vmcs->controls_shadow.tertiary_exec = val; + } +}
Add a "bits" param to the builder macros and use string concatenation, then the tertiary controls can share those macros.
arch/x86/kvm/vmx/vmx.h +19 -19
@@ -398,25 +398,25 @@ static inline u8 vmx_get_rvi(void)return vmcs_read16 (GUEST_INTR_STATUS ) &0xff ; } -#define BUILD_CONTROLS_SHADOW (lname, uname) \ -static inline void lname##_controls_set(struct vcpu_vmx *vmx, u32 val) \ -{ \ - if (vmx->loaded_vmcs->controls_shadow.lname != val) { \ - vmcs_write32(uname, val); \ - vmx->loaded_vmcs->controls_shadow.lname = val; \ - } \ -} \ -static inline u32 lname##_controls_get(struct vcpu_vmx *vmx) \ -{ \ - return vmx->loaded_vmcs->controls_shadow.lname; \ -} \ -static inline void lname##_controls_setbit(struct vcpu_vmx *vmx, u32 val) \ -{ \ - lname##_controls_set(vmx, lname##_controls_get(vmx) | val); \ -} \ -static inline void lname##_controls_clearbit(struct vcpu_vmx *vmx, u32 val) \ -{ \ - lname##_controls_set(vmx, lname##_controls_get(vmx) & ~val); \ +#define BUILD_CONTROLS_SHADOW (lname, uname, bits) \ +static inline void lname##_controls_set(struct vcpu_vmx *vmx, u##bits val) \ +{ \ + if (vmx->loaded_vmcs->controls_shadow.lname != val) { \ + vmcs_write##bits(uname, val); \ + vmx->loaded_vmcs->controls_shadow.lname = val; \ + } \ +} \ +static inline u##bits lname##_controls_get(struct vcpu_vmx *vmx) \ +{ \ + return vmx->loaded_vmcs->controls_shadow.lname; \ +} \ +static inline void lname##_controls_setbit(struct vcpu_vmx *vmx, u##bits val) \ +{ \ + lname##_controls_set(vmx, lname##_controls_get(vmx) | val); \ +} \ +static inline void lname##_controls_clearbit(struct vcpu_vmx *vmx, u##bits val) \ +{ \ + lname##_controls_set(vmx, lname##_controls_get(vmx) & ~val); \ } BUILD_CONTROLS_SHADOW(vm_entry, VM_ENTRY_CONTROLS)BUILD_CONTROLS_SHADOW (vm_exit,VM_EXIT_CONTROLS )
Quoted 7 lines
arch/x86/kvm/vmx/vmx.h +1
-0+static inline void vmx_register_cache_reset (struct kvm_vcpu *vcpu) { vcpu->arch.regs_avail = ~((1 << VCPU_REGS_RIP) | (1 << VCPU_REGS_RSP)Signature · 1 line
1.8.3.1
Re: [RFC PATCH 03/12] kvm/vmx: Introduce the new tertiary processor-based VM-execution controls
Quoted 105 lines · Sean Christopherson
Quoted 6 lines · Robert Hoo
arch/x86/kvm/vmx/vmx.h +0
-0@@ -373,6 +373,14 @@ static inline u8 vmx_get_rvi(void)BUILD_CONTROLS_SHADOW (exec,CPU_BASED_VM_EXEC_CONTROL )arch/x86/kvm/vmx/vmx.h static inline u8 vmx_get_rvi(void) · line 383
Quoted 10 lines
arch/x86/kvm/vmx/vmx.h +7
-0BUILD_CONTROLS_SHADOW(secondary_exec, SECONDARY_VM_EXEC_CONTROL) +static inline void tertiary_exec_controls_set (struct vcpu_vmx *vmx,u64 val) +{ +if (vmx->loaded_vmcs->controls_shadow.tertiary_exec != val) { +vmcs_write64 (TERTIARY_VM_EXEC_CONTROL , val); + vmx->loaded_vmcs->controls_shadow.tertiary_exec = val; + } +}Add a "bits" param to the builder macros and use string concatenation, then the
tertiary controls can share those macros.arch/x86/kvm/vmx/vmx.h +0
-13@@ -398,25 +398,25 @@ static inline u8 vmx_get_rvi(void)return vmcs_read16 (GUEST_INTR_STATUS ) &0xff ; } -#define BUILD_CONTROLS_SHADOW (lname, uname) \ -static inline void lname##_controls_set(struct vcpu_vmx *vmx, u32 val) \ -{ \ -if (vmx->loaded_vmcs->controls_shadow.lname != val) { \ -vmcs_write32 (uname, val); \ - vmx->loaded_vmcs->controls_shadow.lname = val; \ - } \ -} \ -static inline u32 lname##_controls_get(struct vcpu_vmx *vmx) \ -{ \ -return vmx->loaded_vmcs- >controls_shadow.lname; \ -} \ -static inline void lname##_controls_setbit(struct vcpu_vmx *vmx, u32val) \
arch/x86/kvm/vmx/vmx.h +0
-2-{ \ - lname##_controls_set(vmx, lname##_controls_get(vmx) |val); \
arch/x86/kvm/vmx/vmx.h +0
-2-} \ -static inline void lname##_controls_clearbit(struct vcpu_vmx *vmx,u32 val) \
arch/x86/kvm/vmx/vmx.h +0
-2-{ \ - lname##_controls_set(vmx, lname##_controls_get(vmx) &~val); \
+#define BUILD_CONTROLS_SHADOW(lname, uname,
bits) \
+static inline void lname##_controls_set(structvcpu_vmx*vmx,
u##bits val) \arch/x86/kvm/vmx/vmx.h +2
-0+{ \ +if (vmx->loaded_vmcs->controls_shadow.lname != val){ \
+ vmcs_write##bits(uname,
val); \
+vmx->loaded_vmcs->controls_shadow.lname=
val; \arch/x86/kvm/vmx/vmx.h +3
-0+ } \ +} \ +static inline u##bits lname##_controls_get(struct vcpu_vmx*vmx) \
arch/x86/kvm/vmx/vmx.h +2
-0+{ \ + return vmx->loaded_vmcs-Quoted 1 line
arch/x86/kvm/vmx/vmx.h +0
-0controls_shadow.lname; \arch/x86/kvm/vmx/vmx.h +2
-0+} \ +static inline void lname##_controls_setbit(struct vcpu_vmx *vmx,u##bits val) \
arch/x86/kvm/vmx/vmx.h +2
-0+{ \ + lname##_controls_set(vmx, lname##_controls_get(vmx) |val); \
arch/x86/kvm/vmx/vmx.h +2
-0+} \ +static inline void lname##_controls_clearbit(struct vcpu_vmx *vmx,u##bits val) \
arch/x86/kvm/vmx/vmx.h +2
-0+{ \ + lname##_controls_set(vmx, lname##_controls_get(vmx) &
Quoted 5 lines
~val); \
}
BUILD_CONTROLS_SHADOW(vm_entry, VM_ENTRY_CONTROLS)BUILD_CONTROLS_SHADOW(vm_exit, VM_EXIT_CONTROLS)
Nice. I like this. Thanks Sean.
Shall I separated this hunk a patch and have your "Signed-off-by:"?
Quoted 8 lines
Quoted 8 lines
arch/x86/kvm/vmx/vmx.h +1
-0+static inline void vmx_register_cache_reset (struct kvm_vcpu *vcpu){
vcpu->arch.regs_avail= ~((1 <<VCPU_REGS_RIP) | (1 <<VCPU_REGS_RSP)Signature · 1 line
1.8.3.1
RFC PATCH 4/12 kvm/vmx: enable LOADIWKEY vm-exit support in tertiary processor-based VM-execution controls
In reply to Robert HooBut don't implement 'loadiwkey' vm-exit handler in this patch, it will be done in next one.
--- arch/x86/include/asm/vmx.h | 6 ++++++ arch/x86/include/asm/vmxfeatures.h | 3 +++ arch/x86/include/uapi/asm/vmx.h | 5 ++++- arch/x86/kvm/vmx/vmx.c | 27 +++++++++++++++++++++++++++ 4 files changed, 40 insertions(+), 1 deletion(-)
arch/x86/include/asm/vmx.h +6 -0
@@ -75,6 +75,12 @@#define SECONDARY_EXEC_TSC_SCALING VMCS_CONTROL_BIT(TSC_SCALING)#define SECONDARY_EXEC_ENABLE_USR_WAIT_PAUSE VMCS_CONTROL_BIT(USR_WAIT_PAUSE) +/* +* Definitions of Tertiary Processor-Based VM-Execution Controls. +*/ +#define TERTIARY_EXEC_LOADIWKEY_EXITING VMCS_CONTROL_BIT(LOADIWKEY_EXITING) + +#define PIN_BASED_EXT_INTR_MASK VMCS_CONTROL_BIT(INTR_EXITING)#define PIN_BASED_NMI_EXITING VMCS_CONTROL_BIT(NMI_EXITING)#define PIN_BASED_VIRTUAL_NMIS VMCS_CONTROL_BIT(VIRTUAL_NMIS)
arch/x86/include/asm/vmxfeatures.h +3 -0
@@ -85,4 +85,7 @@#define VMX_FEATURE_USR_WAIT_PAUSE ( 2*32+ 26)/* Enable TPAUSE, UMONITOR, UMWAIT in guest */ #define VMX_FEATURE_ENCLV_EXITING ( 2*32+ 28)/* "" VM-Exit on ENCLV (leaf dependent) */ +/* Tertiary Processor-Based VM-Execution Controls, word 3 */ +#define VMX_FEATURE_LOADIWKEY_EXITING (3*32 + 0)/* "" VM-Exit on LOADIWKey */ +#endif /* _ASM_X86_VMXFEATURES_H */
arch/x86/include/uapi/asm/vmx.h +4 -1
@@ -88,6 +88,7 @@#define EXIT_REASON_XRSTORS 64#define EXIT_REASON_UMWAIT 67#define EXIT_REASON_TPAUSE 68 +#define EXIT_REASON_LOADIWKEY 69#define VMX_EXIT_REASONS \ { EXIT_REASON_EXCEPTION_NMI, "EXCEPTION_NMI" }, \
@@ -148,7 +149,9 @@ { EXIT_REASON_XSAVES, "XSAVES" }, \ { EXIT_REASON_XRSTORS, "XRSTORS" }, \ { EXIT_REASON_UMWAIT, "UMWAIT" }, \ - { EXIT_REASON_TPAUSE, "TPAUSE" } + { EXIT_REASON_TPAUSE, "TPAUSE" }, \ + { EXIT_REASON_LOADIWKEY, "LOADIWKEY" } + #define VMX_EXIT_REASON_FLAGS \ { VMX_EXIT_REASONS_FAILED_VMENTRY, "FAILED_VMENTRY" }
arch/x86/kvm/vmx/vmx.c +27 -0
@@ -2368,6 +2368,23 @@ static __init int adjust_vmx_controls(u32 ctl_min, u32 ctl_opt,return 0 ; } +static __init int adjust_vmx_controls_64 (u64 ctl_min,u64 ctl_opt, +u32 msr,u64 *result) +{ +u64 vmx_msr; +u64 ctl = ctl_min | ctl_opt; + +rdmsrl (msr, vmx_msr); + ctl &= vmx_msr;/* bit == 1 means it can be set */ + +/* Ensure minimum (required) set of control bits are supported. */ +if (ctl_min & ~ctl) +return -EIO ; + + *result = ctl; +return 0 ; +} +static __init int setup_vmcs_config (struct vmcs_config *vmcs_conf,struct vmx_capability *vmx_cap) {
@@ -2472,6 +2489,16 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf, "1-setting enable VPID VM-execution control\n"); } +if (_cpu_based_exec_control &CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ) { +u64 opt3 =TERTIARY_EXEC_LOADIWKEY_EXITING ; +u64 min3 =0 ; + +if (adjust_vmx_controls_64 (min3, opt3, +MSR_IA32_VMX_PROCBASED_CTLS3 , + &_cpu_based_3rd_exec_control)) +return -EIO ; + } + min =VM_EXIT_SAVE_DEBUG_CONTROLS |VM_EXIT_ACK_INTR_ON_EXIT ;#ifdef CONFIG_X86_64 min |=VM_EXIT_HOST_ADDR_SPACE_SIZE ;
Signature · 1 line
1.8.3.1
RFC PATCH 5/12 kvm/vmx: Add KVM support on KeyLocker operations
In reply to Robert HooDefine handle_loadiwkey() VM-Exit handler, which fetch the IWKey guest's setting and do it onbehalf. Note LOADIWKEY needs CR4.KeyLocker set. Trap guest write on MSRs of IA32_COPY_LOCAL_TO_PLATFORM and IA32_COPY_PLATFORM_TO_LOCAL_TO_PLATFORM, emulate IWKey save and restore operations.
Trap guest read on MSRs of IA32_COPY_STATUS and IA32_IWKEYBACKUP_STATUS, return their shadow values stored in kvm_vcpu_arch and kvm_arch. Also, guest CPUID.0x19:EBX[0] is dynamic, its status changes as CR4.KL changes.
On each VM-Entry, we need to resotre vCPU's IWKey, stored in kvm_vcpu_arch.
--- arch/x86/include/asm/kvm_host.h | 24 ++++- arch/x86/kvm/cpuid.c | 11 +++ arch/x86/kvm/cpuid.h | 2 + arch/x86/kvm/vmx/vmx.c | 189 ++++++++++++++++++++++++++++++++++++++++ arch/x86/kvm/x86.c | 4 +- arch/x86/kvm/x86.h | 2 + 6 files changed, 229 insertions(+), 3 deletions(-)
arch/x86/include/asm/kvm_host.h +23 -1
@@ -100,7 +100,7 @@ | X86_CR4_PGE | X86_CR4_PCE | X86_CR4_OSFXSR | X86_CR4_PCIDE \ | X86_CR4_OSXSAVE | X86_CR4_SMEP | X86_CR4_FSGSBASE \ | X86_CR4_OSXMMEXCPT | X86_CR4_LA57 | X86_CR4_VMXE \ - | X86_CR4_SMAP | X86_CR4_PKE | X86_CR4_UMIP)) + | X86_CR4_SMAP | X86_CR4_PKE | X86_CR4_UMIP | X86_CR4_KEYLOCKER))#define CR8_RESERVED_BITS (~(unsigned long)X86_CR8_TPR)
@@ -520,6 +520,19 @@ struct kvm_vcpu_hv {cpumask_t tlb_flush; }; +#if defined(CONFIG_ARCH_SUPPORTS_INT128 ) && defined(CONFIG_CC_HAS_INT128 ) +typedef unsigned __int128 u128 ; +#else +typedef struct { +u64 reg64[2 ]; +}u128 ; +#endif + +struct iwkey { +u128 encryption_key[2 ];/* 256bit encryption key */ +u128 integrity_key;/* 128bit integration key */ +}; +struct kvm_vcpu_arch {/* * rip and regs accesses must go through
@@ -805,6 +818,11 @@ struct kvm_vcpu_arch {*/ bool enforce; } pv_cpuid; + +/* Intel KeyLocker */ +bool iwkey_loaded; +struct iwkey iwkey; +u32 msr_ia32_copy_status; };struct kvm_lpage_info {
@@ -931,6 +949,10 @@ struct kvm_arch {bool apic_access_page_done;unsigned long apicv_inhibit_reasons; +bool iwkey_backup_valid; +u32 msr_ia32_iwkey_backup_status; +struct iwkey iwkey_backup; +gpa_t wall_clock;bool mwait_in_guest;
arch/x86/kvm/cpuid.c +11 -0
@@ -133,6 +133,12 @@ void kvm_update_cpuid_runtime(struct kvm_vcpu *vcpu) cpuid_entry_has(best, X86_FEATURE_XSAVEC))) best->ebx = xstate_required_size(vcpu->arch.xcr0, true); +/* update CPUID.0x19.EBX[0], depends on CR4.KL */ + best =kvm_find_cpuid_entry (vcpu,0x19 ,0 ); +if (best) +cpuid_entry_change (best,X86_FEATURE_KL_INS_ENABLED , +kvm_read_cr4_bits (vcpu,X86_CR4_KEYLOCKER )); + best =kvm_find_cpuid_entry (vcpu,KVM_CPUID_FEATURES ,0 );if (kvm_hlt_in_guest (vcpu->kvm) && best && (best->eax & (1 <<KVM_FEATURE_PV_UNHALT )))
@@ -407,6 +413,11 @@ void kvm_set_cpu_caps(void)if (cpuid_ecx (7 ) &F (LA57 ))kvm_cpu_cap_set (X86_FEATURE_LA57 ); +/* At present, host and guest can only exclusively use KeyLocker */ +if (!boot_cpu_has (X86_FEATURE_KEYLOCKER ) && (cpuid_ecx (0x7 ) & +feature_bit (KEYLOCKER ))) +kvm_cpu_cap_set (X86_FEATURE_KEYLOCKER ); +/* * PKU not yet implemented for shadow paging and requires OSPKE * to be set on the host. Clear it if that is not the case
arch/x86/kvm/cpuid.h +2 -0
@@ -63,6 +63,8 @@ struct cpuid_reg { [CPUID_8000_0007_EBX] = {0x80000007, 0, CPUID_EBX}, [CPUID_7_EDX] = { 7, 0, CPUID_EDX}, [CPUID_7_1_EAX] = { 7, 1, CPUID_EAX}, + [CPUID_19_EBX] = { 0x19, 0, CPUID_EBX}, + [CPUID_19_ECX] = { 0x19, 0, CPUID_ECX}, };/*
arch/x86/kvm/vmx/vmx.c +189 -0
231 lines not on this page · raw message
arch/x86/kvm/x86.c +2 -2
@@ -1013,7 +1013,7 @@ int kvm_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4) (!(cr4 & X86_CR4_PCIDE) && (old_cr4 & X86_CR4_PCIDE)))kvm_mmu_reset_context (vcpu); -if ((cr4 ^ old_cr4) & (X86_CR4_OSXSAVE |X86_CR4_PKE )) +if ((cr4 ^ old_cr4) & (X86_CR4_OSXSAVE |X86_CR4_PKE |X86_CR4_KEYLOCKER ))kvm_update_cpuid_runtime (vcpu);return 0 ;
@@ -9598,7 +9598,7 @@ static int __set_sregs(struct kvm_vcpu *vcpu, struct kvm_sregs *sregs) mmu_reset_needed |=kvm_read_cr4 (vcpu) != sregs->cr4; cpuid_update_needed |= ((kvm_read_cr4 (vcpu) ^ sregs->cr4) & - (X86_CR4_OSXSAVE |X86_CR4_PKE )); + (X86_CR4_OSXSAVE |X86_CR4_PKE |X86_CR4_KEYLOCKER )); kvm_x86_ops.set_cr4 (vcpu, sregs->cr4);if (cpuid_update_needed)kvm_update_cpuid_runtime (vcpu);
arch/x86/kvm/x86.h +2 -0
@@ -404,6 +404,8 @@ int kvm_handle_memory_failure(struct kvm_vcpu *vcpu, int r, __reserved_bits |=X86_CR4_UMIP ; \if (!__cpu_has (__c,X86_FEATURE_VMX )) \ __reserved_bits |=X86_CR4_VMXE ; \ +if (!__cpu_has (__c,X86_FEATURE_KEYLOCKER )) \ + __reserved_bits |=X86_CR4_KEYLOCKER ; \ __reserved_bits; \ })
Signature · 1 line
1.8.3.1
Sean Christopherson
maintainerRe: [RFC PATCH 05/12] kvm/vmx: Add KVM support on KeyLocker operations
Quoted 1 line · Robert Hoo
On each VM-Entry, we need to resotre vCPU's IWKey, stored in
kvm_vcpu_arch.
...
Quoted 48 lines
arch/x86/kvm/vmx/vmx.c +48
-0+static int get_xmm (int index,u128 *mem_ptr) +{ +int ret =0 ; + + asm ("cli" ); +switch (index) { +case 0 : + asm ("movdqu %%xmm0, %0" : :"m" (*mem_ptr)); +break ; +case 1 : + asm ("movdqu %%xmm1, %0" : :"m" (*mem_ptr)); +break ; +case 2 : + asm ("movdqu %%xmm2, %0" : :"m" (*mem_ptr)); +break ; +case 3 : + asm ("movdqu %%xmm3, %0" : :"m" (*mem_ptr)); +break ; +case 4 : + asm ("movdqu %%xmm4, %0" : :"m" (*mem_ptr)); +break ; +case 5 : + asm ("movdqu %%xmm5, %0" : :"m" (*mem_ptr)); +break ; +case 6 : + asm ("movdqu %%xmm6, %0" : :"m" (*mem_ptr)); +break ; +case 7 : + asm ("movdqu %%xmm7, %0" : :"m" (*mem_ptr)); +break ; +#ifdef CONFIG_X86_64 +case 8 : + asm ("movdqu %%xmm8, %0" : :"m" (*mem_ptr)); +break ; +case 9 : + asm ("movdqu %%xmm9, %0" : :"m" (*mem_ptr)); +break ; +case 10 : + asm ("movdqu %%xmm10, %0" : :"m" (*mem_ptr)); +break ; +case 11 : + asm ("movdqu %%xmm11, %0" : :"m" (*mem_ptr)); +break ; +case 12 : + asm ("movdqu %%xmm12, %0" : :"m" (*mem_ptr)); +break ; +case 13 : + asm ("movdqu %%xmm13, %0" : :"m" (*mem_ptr));
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel, · line 1253
Quoted 10 lines
arch/x86/kvm/vmx/vmx.c +10
-0+break ; +case 14 : + asm ("movdqu %%xmm14, %0" : :"m" (*mem_ptr)); +break ; +case 15 : + asm ("movdqu %%xmm15, %0" : :"m" (*mem_ptr)); +break ; +#endif +default : +pr_err_once ("xmm index exceeds" );
That error message is not remotely helpful. If this theoretically reachable, make it a WARN.
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel,
Quoted 4 lines
arch/x86/kvm/vmx/vmx.c +4
-0+ ret =-1 ; +break ; + } + asm ("sti" );a
Don't code IRQ disabling/enabling. Second, why are IRQs being disabled in this low level helper?
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel, · line 1266
Quoted 9 lines
arch/x86/kvm/vmx/vmx.c +9
-0+ +return ret; +} + +static void vmx_load_guest_iwkey (struct kvm_vcpu *vcpu) +{ +u128 xmm[3 ] = {0 }; + +if (vcpu->arch.iwkey_loaded) {
Loading the IWKey is not tied to the guest/host context switch. IIUC, the intent is to leave the IWKey in hardware while the host is running. I.e. KVM should be able to track which key is current resident in hardware separately from the guest/host stuff.
And loading the IWKey only on VM-Enter iff the guest loaded a key means KVM is leaking one VM's IWKey to all other VMs with KL enabled but that haven't loaded their own IWKey. To prevent leaking a key, KVM would need to load the new vCPU's key, even if it's "null", if the old vCPU _or_ the new vCPU has loaded a key.
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel, · line 1279
Quoted 13 lines
arch/x86/kvm/vmx/vmx.c +13
-0+bool clear_cr4 = false; +/* Save origin %xmm */ +get_xmm (0 , &xmm[0 ]); +get_xmm (1 , &xmm[1 ]); +get_xmm (2 , &xmm[2 ]); + + asm ("movdqu %0, %%xmm0;" +"movdqu %1, %%xmm1;" +"movdqu %2, %%xmm2;" + : :"m" (vcpu->arch.iwkey.integrity_key), +"m" (vcpu->arch.iwkey.encryption_key[0 ]), +"m" (vcpu->arch.iwkey.encryption_key[1 ])); +if (!(cr4_read_shadow () &X86_CR4_KEYLOCKER )) {
Presumably this should assert that CR4.KL=0, otherwise it means the guest's key is effectively being leaked to userspace.
Quoted 29 lines
arch/x86/kvm/vmx/vmx.c +19
-0+cr4_set_bits (X86_CR4_KEYLOCKER ); + clear_cr4 = true; + } + asm volatile(LOADIWKEY : : "a" (0x0)); +if (clear_cr4) +cr4_clear_bits (X86_CR4_KEYLOCKER ); +/* restore %xmm */ + asm ("movdqu %0, %%xmm0;" +"movdqu %1, %%xmm1;" +"movdqu %2, %%xmm2;" + : :"m" (xmm[0 ]), +"m" (xmm[1 ]), +"m" (xmm[2 ])); + } +} +void vmx_prepare_switch_to_guest (struct kvm_vcpu *vcpu) {struct vcpu_vmx *vmx =to_vmx (vcpu);@@ -1260,6 +1361,9 @@ void vmx_prepare_switch_to_guest(struct kvm_vcpu *vcpu)#endif vmx_set_host_fs_gs (host_state, fs_sel, gs_sel, fs_base, gs_base); + +vmx_load_guest_iwkey (vcpu); + vmx->guest_state_loaded = true; }
Re: [RFC PATCH 05/12] kvm/vmx: Add KVM support on KeyLocker operations
Quoted 60 lines · Sean Christopherson
Quoted 2 lines · Robert Hoo
On each VM-Entry, we need to resotre vCPU's IWKey, stored in
kvm_vcpu_arch....
Quoted 54 lines
arch/x86/kvm/vmx/vmx.c +54
-0+static int get_xmm (int index,u128 *mem_ptr) +{ +int ret =0 ; + + asm ("cli" ); +switch (index) { +case 0 : + asm ("movdqu %%xmm0, %0" : :"m" (*mem_ptr)); +break ; +case 1 : + asm ("movdqu %%xmm1, %0" : :"m" (*mem_ptr)); +break ; +case 2 : + asm ("movdqu %%xmm2, %0" : :"m" (*mem_ptr)); +break ; +case 3 : + asm ("movdqu %%xmm3, %0" : :"m" (*mem_ptr)); +break ; +case 4 : + asm ("movdqu %%xmm4, %0" : :"m" (*mem_ptr)); +break ; +case 5 : + asm ("movdqu %%xmm5, %0" : :"m" (*mem_ptr)); +break ; +case 6 : + asm ("movdqu %%xmm6, %0" : :"m" (*mem_ptr)); +break ; +case 7 : + asm ("movdqu %%xmm7, %0" : :"m" (*mem_ptr)); +break ; +#ifdef CONFIG_X86_64 +case 8 : + asm ("movdqu %%xmm8, %0" : :"m" (*mem_ptr)); +break ; +case 9 : + asm ("movdqu %%xmm9, %0" : :"m" (*mem_ptr)); +break ; +case 10 : + asm ("movdqu %%xmm10, %0" : :"m" (*mem_ptr)); +break ; +case 11 : + asm ("movdqu %%xmm11, %0" : :"m" (*mem_ptr)); +break ; +case 12 : + asm ("movdqu %%xmm12, %0" : :"m" (*mem_ptr)); +break ; +case 13 : + asm ("movdqu %%xmm13, %0" : :"m" (*mem_ptr)); +break ; +case 14 : + asm ("movdqu %%xmm14, %0" : :"m" (*mem_ptr)); +break ; +case 15 : + asm ("movdqu %%xmm15, %0" : :"m" (*mem_ptr));
Quoted 8 lines
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel, · line 1253
Quoted 4 lines
arch/x86/kvm/vmx/vmx.c +4
-0+break ; +#endif +default : +pr_err_once ("xmm index exceeds" );That error message is not remotely helpful. If this theoretically reachable,
make it a WARN.
At this moment, not theoretically reachable.
It's my habit to always worry for future careless callers. OK, remove it.
Quoted 9 lines
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel,
Quoted 5 lines
arch/x86/kvm/vmx/vmx.c +4
-0+ ret =-1 ; +break ; + } + asm ("sti" );aDon't code IRQ disabling/enabling. Second, why are IRQs being disabled in this
low level helper?
Looks it's unnecessary. Going to remove it.
Quoted 11 lines
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel, · line 1266
Quoted 10 lines
arch/x86/kvm/vmx/vmx.c +9
-0+ +return ret; +} + +static void vmx_load_guest_iwkey (struct kvm_vcpu *vcpu) +{ +u128 xmm[3 ] = {0 }; + +if (vcpu->arch.iwkey_loaded) {
Quoted 7 lines
Loading the IWKey is not tied to the guest/host context switch. IIUC, the intent
is to leave the IWKey in hardware while the host is running. I.e. KVM should be
able to track which key is current resident in hardware separately from the
guest/host stuff.
In current phase, guest and host can only exclusively use Key Locker, so, more precisely saying, KVM should be able to track which guest IWKey is in hardware.
Yes your point is right, load a vCPU's IWKey is not necessary every time enter guest, e.g. no vCPU switching happened.
My above implementation is simply the logic, but your suggestion is more efficiency-saving.
I'm going to implement this in next version: only load vCPU's IWKey on its switching to another pCPU.
Quoted 9 lines
And loading the IWKey only on VM-Enter iff the guest loaded a key means KVM is
leaking one VM's IWKey to all other VMs with KL enabled but that haven't loaded
their own IWKey. To prevent leaking a key, KVM would need to load the new vCPU's
key, even if it's "null", if the old vCPU _or_ the new vCPU has loaded a key.
Right. Thanks for your careful review.
Quoted 10 lines
Quoted 10 lines
arch/x86/kvm/vmx/vmx.c +9
-0+bool clear_cr4 = false; +/* Save origin %xmm */ +get_xmm (0 , &xmm[0 ]); +get_xmm (1 , &xmm[1 ]); +get_xmm (2 , &xmm[2 ]); + + asm ("movdqu %0, %%xmm0;" +"movdqu %1, %%xmm1;" + "movdqu %2, %%xmm2;"
Quoted 8 lines
arch/x86/kvm/vmx/vmx.c void vmx_set_host_fs_gs(struct vmcs_host_state *host, u16 fs_sel, u16 gs_sel, · line 1279
Quoted 4 lines
arch/x86/kvm/vmx/vmx.c +4
-0+ : : "m"(vcpu->arch.iwkey.integrity_key), +"m" (vcpu->arch.iwkey.encryption_key[0 ]), + "m"(vcpu->arch.iwkey.encryption_key[1])); +if (!(cr4_read_shadow () &X86_CR4_KEYLOCKER )) {Presumably this should assert that CR4.KL=0, otherwise it means the guest's key
is effectively being leaked to userspace.
OK, for current phase of host/guest exclusively have Key Locker feature.
Quoted 32 lines
Quoted 32 lines
arch/x86/kvm/vmx/vmx.c +19
-0+cr4_set_bits (X86_CR4_KEYLOCKER ); + clear_cr4 = true; + } + asm volatile(LOADIWKEY : : "a" (0x0)); +if (clear_cr4) +cr4_clear_bits (X86_CR4_KEYLOCKER ); +/* restore %xmm */ + asm ("movdqu %0, %%xmm0;" +"movdqu %1, %%xmm1;" +"movdqu %2, %%xmm2;" + : :"m" (xmm[0 ]), +"m" (xmm[1 ]), +"m" (xmm[2 ])); + } +} +void vmx_prepare_switch_to_guest (struct kvm_vcpu *vcpu) {struct vcpu_vmx *vmx =to_vmx (vcpu);@@ -1260,6 +1361,9 @@ void vmx_prepare_switch_to_guest(struct kvm_vcpu *vcpu)#endif vmx_set_host_fs_gs (host_state, fs_sel, gs_sel, fs_base, gs_base); + +vmx_load_guest_iwkey (vcpu); + vmx->guest_state_loaded = true;}
RFC PATCH 6/12 kvm/cpuid: Enumerate KeyLocker feature in KVM
In reply to Robert HooIn kvm_set_cpu_caps(), add KeyLocker feature enumeration, under the condition that 1) HW supports this feature 2) host Kernel isn't enabled with this feature.
Filter out randomization support bit (CPUID.0x19.ECX[1]), as by design it cannot be supported at this moment.
--- arch/x86/kvm/cpuid.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)
arch/x86/kvm/cpuid.c +13 -2
@@ -406,9 +406,10 @@ void kvm_set_cpu_caps(void)kvm_cpu_cap_mask (CPUID_7_ECX ,F (AVX512VBMI ) |F (LA57 ) |F (PKU ) |0 /*OSPKE*/ |F (RDPID ) |F (AVX512_VPOPCNTDQ ) |F (UMIP ) |F (AVX512_VBMI2 ) |F (GFNI ) | -F (VAES ) |F (VPCLMULQDQ ) |F (AVX512_VNNI ) |F (AVX512_BITALG ) | -F (CLDEMOTE ) |F (MOVDIRI ) |F (MOVDIR64B ) |0 /*WAITPKG*/ +F (VAES ) |0 /*KEYLOCKER*/ |F (VPCLMULQDQ ) |F (AVX512_VNNI ) | +F (AVX512_BITALG ) |F (CLDEMOTE ) |F (MOVDIRI ) |F (MOVDIR64B ) |0 /*WAITPKG*/ ); +/* Set LA57 based on hardware capability. */ if (cpuid_ecx (7 ) &F (LA57 ))kvm_cpu_cap_set (X86_FEATURE_LA57 );
@@ -451,6 +452,11 @@ void kvm_set_cpu_caps(void)F (XSAVEOPT ) |F (XSAVEC ) |F (XGETBV1 ) |F (XSAVES ) ); +kvm_cpu_cap_mask (CPUID_19_EBX ,F (KL_INS_ENABLED ) |F (KL_WIDE ) | +F (IWKEY_BACKUP )); +/* No randomize exposed to guest */ +kvm_cpu_cap_mask (CPUID_19_ECX ,F (IWKEY_NOBACKUP )); + kvm_cpu_cap_mask(CPUID_8000_0001_ECX, F(LAHF_LM) | F(CMP_LEGACY) | 0 /*SVM*/ | 0 /* ExtApicSpace */ | F(CR8_LEGACY) | F(ABM) | F(SSE4A) | F(MISALIGNSSE) |
@@ -784,6 +790,11 @@ static inline int __do_cpuid_func(struct kvm_cpuid_array *array, u32 function) goto out; }break ; +/* KeyLocker */ +case 0x19 : +cpuid_entry_override (entry,CPUID_19_ECX ); +break ; +case KVM_CPUID_SIGNATURE : {static const char signature[12 ] ="KVMKVMKVM\0\0" ;const u32 *sigptr = (const u32 *)signature;
Signature · 1 line
1.8.3.1
RFC PATCH 7/12 kvm/vmx/nested: Support new IA32_VMX_PROCBASED_CTLS3 vmx feature control MSR
In reply to Robert HooAdd this new VMX feature MSR in nested_vmx_msrs, for the Tertiary Proc-based Exec-Control nested support.
Don't set its LOADIWKEY VM-Exit bit at present. It will be enabled in last patch when everything's prepared.
--- arch/x86/kvm/vmx/capabilities.h | 2 ++ arch/x86/kvm/vmx/nested.c | 18 +++++++++++++++++- arch/x86/kvm/vmx/vmx.c | 6 +++--- arch/x86/kvm/x86.c | 2 ++ 4 files changed, 24 insertions(+), 4 deletions(-)
arch/x86/kvm/vmx/capabilities.h +2 -0
@@ -30,6 +30,8 @@ struct nested_vmx_msrs {u32 procbased_ctls_high;u32 secondary_ctls_low;u32 secondary_ctls_high; +/* Tertiary Controls is 64bit allow-1 semantics */ +u64 tertiary_ctls;u32 pinbased_ctls_low;u32 pinbased_ctls_high;u32 exit_ctls_low;
arch/x86/kvm/vmx/nested.c +17 -1
@@ -1285,6 +1285,13 @@ static int vmx_restore_vmx_basic(struct vcpu_vmx *vmx, u64 data) lowp = &vmx->nested.msrs.secondary_ctls_low; highp = &vmx->nested.msrs.secondary_ctls_high;break ; +/* +* MSR_IA32_VMX_PROCBASED_CTLS3 is 64bit, all allow-1. +* No need to check. Just return. +*/ +case MSR_IA32_VMX_PROCBASED_CTLS3 : + vmx->nested.msrs.tertiary_ctls = data; +return 0 ;default :BUG (); }
@@ -1421,6 +1428,7 @@ int vmx_set_vmx_msr(struct kvm_vcpu *vcpu, u32 msr_index, u64 data)case MSR_IA32_VMX_TRUE_EXIT_CTLS :case MSR_IA32_VMX_TRUE_ENTRY_CTLS :case MSR_IA32_VMX_PROCBASED_CTLS2 : +case MSR_IA32_VMX_PROCBASED_CTLS3 :return vmx_restore_control_msr (vmx, msr_index, data);case MSR_IA32_VMX_MISC :return vmx_restore_vmx_misc (vmx, data);
@@ -1516,6 +1524,9 @@ int vmx_get_vmx_msr(struct nested_vmx_msrs *msrs, u32 msr_index, u64 *pdata) msrs->secondary_ctls_low, msrs->secondary_ctls_high);break ; +case MSR_IA32_VMX_PROCBASED_CTLS3 : + *pdata = msrs->tertiary_ctls; +break ;case MSR_IA32_VMX_EPT_VPID_CAP : *pdata = msrs->ept_caps | ((u64 )msrs->vpid_caps <<32 );
@@ -6375,7 +6386,8 @@ void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps)CPU_BASED_USE_IO_BITMAPS |CPU_BASED_MONITOR_TRAP_FLAG |CPU_BASED_MONITOR_EXITING |CPU_BASED_RDPMC_EXITING |CPU_BASED_RDTSC_EXITING |CPU_BASED_PAUSE_EXITING | -CPU_BASED_TPR_SHADOW |CPU_BASED_ACTIVATE_SECONDARY_CONTROLS ; +CPU_BASED_TPR_SHADOW |CPU_BASED_ACTIVATE_SECONDARY_CONTROLS | +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ;/* * We can allow some features even when not supported by the * hardware. For example, L1 can specify an MSR bitmap - and we
@@ -6413,6 +6425,10 @@ void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps)SECONDARY_EXEC_RDSEED_EXITING |SECONDARY_EXEC_XSAVES ; +if (msrs->procbased_ctls_high &CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ) +rdmsrl (MSR_IA32_VMX_PROCBASED_CTLS3 , + msrs->tertiary_ctls); + msrs->tertiary_ctls &= ~TERTIARY_EXEC_LOADIWKEY_EXITING ;/* * We can emulate "VMCS shadowing," even if the hardware * doesn't support it.
arch/x86/kvm/vmx/vmx.c +3 -3
@@ -1880,7 +1880,7 @@ static inline bool vmx_feature_control_msr_valid(struct kvm_vcpu *vcpu,static int vmx_get_msr_feature (struct kvm_msr_entry *msr) {switch (msr->index) { - case MSR_IA32_VMX_BASIC ... MSR_IA32_VMX_VMFUNC: + case MSR_IA32_VMX_BASIC ... MSR_IA32_VMX_PROCBASED_CTLS3:if (!nested)return 1 ;return vmx_get_vmx_msr (&vmcs_config.nested, msr->index, &msr->data);
@@ -1961,7 +1961,7 @@ static int vmx_get_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)case MSR_IA32_FEAT_CTL : msr_info->data = vmx->msr_ia32_feature_control;break ; - case MSR_IA32_VMX_BASIC ... MSR_IA32_VMX_VMFUNC: + case MSR_IA32_VMX_BASIC ... MSR_IA32_VMX_PROCBASED_CTLS3:if (!nested_vmx_allowed (vcpu))return 1 ; if (vmx_get_vmx_msr(&vmx->nested.msrs, msr_info->index,
@@ -2240,7 +2240,7 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)if (msr_info->host_initiated && data ==0 )vmx_leave_nested (vcpu);break ; - case MSR_IA32_VMX_BASIC ... MSR_IA32_VMX_VMFUNC: + case MSR_IA32_VMX_BASIC ... MSR_IA32_VMX_PROCBASED_CTLS3:if (!msr_info->host_initiated)return 1 ;/* they are read-only */ if (!nested_vmx_allowed (vcpu))
arch/x86/kvm/x86.c +2 -0
@@ -1300,6 +1300,7 @@ bool kvm_rdpmc(struct kvm_vcpu *vcpu)MSR_IA32_VMX_PROCBASED_CTLS2 ,MSR_IA32_VMX_EPT_VPID_CAP ,MSR_IA32_VMX_VMFUNC , +MSR_IA32_VMX_PROCBASED_CTLS3 ,MSR_K7_HWCR , MSR_KVM_POLL_CONTROL,
@@ -1331,6 +1332,7 @@ bool kvm_rdpmc(struct kvm_vcpu *vcpu)MSR_IA32_VMX_PROCBASED_CTLS2 ,MSR_IA32_VMX_EPT_VPID_CAP ,MSR_IA32_VMX_VMFUNC , +MSR_IA32_VMX_PROCBASED_CTLS3 ,MSR_F10H_DECFG , MSR_IA32_UCODE_REV,
Signature · 1 line
1.8.3.1
Sean Christopherson
maintainerRe: [RFC PATCH 07/12] kvm/vmx/nested: Support new IA32_VMX_PROCBASED_CTLS3 vmx feature control MSR
arch/x86/kvm/vmx/nested.c static int vmx_restore_vmx_basic(struct vcpu_vmx *vmx, u64 data) · line 1290
Quoted 11 lines · Robert Hoo
arch/x86/kvm/vmx/nested.c +3
-0@@ -1285,6 +1285,13 @@ static int vmx_restore_vmx_basic(struct vcpu_vmx *vmx, u64 data) lowp = &vmx->nested.msrs.secondary_ctls_low; highp = &vmx->nested.msrs.secondary_ctls_high;break ; +/* +* MSR_IA32_VMX_PROCBASED_CTLS3 is 64bit, all allow-1. +* No need to check. Just return.
Uh, yes need to check. Unsupported bits need to be '0'.
Quoted 36 lines
arch/x86/kvm/vmx/nested.c +10
-1+*/ +case MSR_IA32_VMX_PROCBASED_CTLS3 : + vmx->nested.msrs.tertiary_ctls = data; +return 0 ;default :BUG (); }@@ -1421,6 +1428,7 @@ int vmx_set_vmx_msr(struct kvm_vcpu *vcpu, u32 msr_index, u64 data)case MSR_IA32_VMX_TRUE_EXIT_CTLS :case MSR_IA32_VMX_TRUE_ENTRY_CTLS :case MSR_IA32_VMX_PROCBASED_CTLS2 : +case MSR_IA32_VMX_PROCBASED_CTLS3 :return vmx_restore_control_msr (vmx, msr_index, data);case MSR_IA32_VMX_MISC :return vmx_restore_vmx_misc (vmx, data);@@ -1516,6 +1524,9 @@ int vmx_get_vmx_msr(struct nested_vmx_msrs *msrs, u32 msr_index, u64 *pdata) msrs->secondary_ctls_low, msrs->secondary_ctls_high);break ; +case MSR_IA32_VMX_PROCBASED_CTLS3 : + *pdata = msrs->tertiary_ctls; +break ;case MSR_IA32_VMX_EPT_VPID_CAP : *pdata = msrs->ept_caps | ((u64 )msrs->vpid_caps <<32 );@@ -6375,7 +6386,8 @@ void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps)CPU_BASED_USE_IO_BITMAPS |CPU_BASED_MONITOR_TRAP_FLAG |CPU_BASED_MONITOR_EXITING |CPU_BASED_RDPMC_EXITING |CPU_BASED_RDTSC_EXITING |CPU_BASED_PAUSE_EXITING | -CPU_BASED_TPR_SHADOW |CPU_BASED_ACTIVATE_SECONDARY_CONTROLS ; +CPU_BASED_TPR_SHADOW |CPU_BASED_ACTIVATE_SECONDARY_CONTROLS | +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ;/* * We can allow some features even when not supported by the * hardware. For example, L1 can specify an MSR bitmap - and we
arch/x86/kvm/vmx/nested.c void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps) · line 6430
Quoted 6 lines
arch/x86/kvm/vmx/nested.c +3
-0@@ -6413,6 +6425,10 @@ void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps)SECONDARY_EXEC_RDSEED_EXITING |SECONDARY_EXEC_XSAVES ; +if (msrs->procbased_ctls_high &CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ) +rdmsrl (MSR_IA32_VMX_PROCBASED_CTLS3 , + msrs->tertiary_ctls);
No need to split that into two lines.
arch/x86/kvm/vmx/nested.c void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps) · line 6431
Quoted 1 line
arch/x86/kvm/vmx/nested.c +1
-0+ msrs->tertiary_ctls &= ~TERTIARY_EXEC_LOADIWKEY_EXITING ;
That's wrong, it should simply be "msrs->tertiary_ctls &= 0" until LOADIWKEY is supported.
Quoted 3 lines
arch/x86/kvm/vmx/nested.c +0
-0/* * We can emulate "VMCS shadowing," even if the hardware * doesn't support it.
Re: [RFC PATCH 07/12] kvm/vmx/nested: Support new IA32_VMX_PROCBASED_CTLS3 vmx feature control MSR
Quoted 15 lines · Sean Christopherson
arch/x86/kvm/vmx/nested.c static int vmx_restore_vmx_basic(struct · line 1291
Quoted 12 lines · Robert Hoo
arch/x86/kvm/vmx/nested.c +3
-0@@ -1285,6 +1285,13 @@ static int vmx_restore_vmx_basic(struct vcpu_vmx *vmx, u64 data) lowp = &vmx->nested.msrs.secondary_ctls_low; highp = &vmx->nested.msrs.secondary_ctls_high;break ; +/* +* MSR_IA32_VMX_PROCBASED_CTLS3 is 64bit, all allow-1. +* No need to check. Just return. Uh, yes need to check. Unsupported bits need to be '0'.
Right! Thanks Sean. Going to refactor this function.
Quoted 47 lines
Quoted 47 lines
arch/x86/kvm/vmx/nested.c +4
-0+*/ +case MSR_IA32_VMX_PROCBASED_CTLS3 : + vmx->nested.msrs.tertiary_ctls = data; +return 0 ;default :BUG ();arch/x86/kvm/vmx/nested.c +1
-0}@@ -1421,6 +1428,7 @@ int vmx_set_vmx_msr(struct kvm_vcpu *vcpu, u32 msr_index, u64 data)case MSR_IA32_VMX_TRUE_EXIT_CTLS :case MSR_IA32_VMX_TRUE_ENTRY_CTLS :case MSR_IA32_VMX_PROCBASED_CTLS2 : +case MSR_IA32_VMX_PROCBASED_CTLS3 :return vmx_restore_control_msr (vmx, msr_index, data);case MSR_IA32_VMX_MISC :arch/x86/kvm/vmx/nested.c +3
-0return vmx_restore_vmx_misc (vmx, data);@@ -1516,6 +1524,9 @@ int vmx_get_vmx_msr(struct nested_vmx_msrs *msrs, u32 msr_index, u64 *pdata) msrs->secondary_ctls_low, msrs->secondary_ctls_high);break ; +case MSR_IA32_VMX_PROCBASED_CTLS3 : + *pdata = msrs->tertiary_ctls; +break ;case MSR_IA32_VMX_EPT_VPID_CAP : *pdata = msrs->ept_caps |arch/x86/kvm/vmx/nested.c +0
-0((u64 )msrs->vpid_caps <<32 );@@ -6375,7 +6386,8 @@ void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps) CPU_BASED_USE_IO_BITMAPS | CPU_BASED_MONITOR_TRAP_FLAG|
arch/x86/kvm/vmx/nested.c +0
-1CPU_BASED_MONITOR_EXITING |CPU_BASED_RDPMC_EXITING | CPU_BASED_RDTSC_EXITING | CPU_BASED_PAUSE_EXITING | - CPU_BASED_TPR_SHADOW |
CPU_BASED_ACTIVATE_SECONDARY_CONTROLS;arch/x86/kvm/vmx/nested.c +1
-0+ CPU_BASED_TPR_SHADOW |
CPU_BASED_ACTIVATE_SECONDARY_CONTROLS|arch/x86/kvm/vmx/nested.c +1
-0+CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ;/* * We can allow some features even when not supported by the * hardware. For example, L1 can specify an MSR bitmap - and we @@ -6413,6 +6425,10 @@ void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps) SECONDARY_EXEC_RDSEED_EXITING |SECONDARY_EXEC_XSAVES ;
Quoted 6 lines
arch/x86/kvm/vmx/nested.c void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps) · line 6430
Quoted 4 lines
arch/x86/kvm/vmx/nested.c +3
-0+if (msrs->procbased_ctls_high &CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ) +rdmsrl (MSR_IA32_VMX_PROCBASED_CTLS3 , + msrs->tertiary_ctls);No need to split that into two lines.
OK
Quoted 6 lines
arch/x86/kvm/vmx/nested.c void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps) · line 6431
Quoted 2 lines
arch/x86/kvm/vmx/nested.c +1
-0+ msrs->tertiary_ctls &= ~TERTIARY_EXEC_LOADIWKEY_EXITING ;That's wrong, it should simply be "
msrs->tertiary_ctls&= 0" until LOADIWKEY is
supported.
OK, after pondering, yes, you're right.
Since tertiary_ctls is allow-1 semantics, it shall imitate secondary_ctls_high.
Look at above code
msrs->secondary_ctls_high &= SECONDARY_EXEC_DESC | SECONDARY_EXEC_ENABLE_RDTSCP | SECONDARY_EXEC_VIRTUALIZE_X2APIC_MODE | SECONDARY_EXEC_WBINVD_EXITING | SECONDARY_EXEC_APIC_REGISTER_VIRT | SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY | SECONDARY_EXEC_RDRAND_EXITING | SECONDARY_EXEC_ENABLE_INVPCID | SECONDARY_EXEC_RDSEED_EXITING | SECONDARY_EXEC_XSAVES;
secondary_ctls_high clears all native set-bits but leaves some by purpose.
Is this what your mean?
Quoted 4 lines
Quoted 4 lines
arch/x86/kvm/vmx/nested.c +0
-0/* arch/x86/kvm/vmx/nested.c +0
-0* We can emulate "VMCS shadowing," even if the hardware * doesn't support it.
RFC PATCH 8/12 kvm/vmx: Refactor vmx_compute_tertiary_exec_control()
In reply to Robert HooLike vmx_compute_tertiary_exec_control(), before L1 set VMCS, compute its nested VMX feature control MSR's value according to guest CPUID setting.
--- arch/x86/kvm/vmx/vmx.c | 22 +++++++++++++++++----- arch/x86/kvm/vmx/vmx.h | 1 + 2 files changed, 18 insertions(+), 5 deletions(-)
arch/x86/kvm/vmx/vmx.c +17 -5
@@ -4377,10 +4377,20 @@ u32 vmx_exec_control(struct vcpu_vmx *vmx)#define vmx_adjust_sec_exec_exiting (vmx, exec_control, lname, uname) \ vmx_adjust_sec_exec_control(vmx, exec_control, lname, uname, uname##_EXITING, true) -static u64 vmx_tertiary_exec_control (struct vcpu_vmx *vmx) +static void vmx_compute_tertiary_exec_control (struct vcpu_vmx *vmx) { -/* Though currently, no special adjustment. There might be in the future*/ -return vmcs_config.cpu_based_3rd_exec_ctrl; +struct kvm_vcpu *vcpu = &vmx->vcpu; +u32 exec_control = vmcs_config.cpu_based_3rd_exec_ctrl; + +if (nested) { +if (guest_cpuid_has (vcpu,X86_FEATURE_KEYLOCKER )) + vmx->nested.msrs.tertiary_ctls |= +TERTIARY_EXEC_LOADIWKEY_EXITING ; +else + vmx->nested.msrs.tertiary_ctls &= + ~TERTIARY_EXEC_LOADIWKEY_EXITING ; + } + vmx->tertiary_exec_control = exec_control; }static void vmx_compute_secondary_exec_control (struct vcpu_vmx *vmx)
@@ -4493,8 +4503,10 @@ static void init_vmcs(struct vcpu_vmx *vmx)secondary_exec_controls_set (vmx, vmx->secondary_exec_control); } -if (cpu_has_tertiary_exec_ctrls ()) -tertiary_exec_controls_set (vmx,vmx_tertiary_exec_control (vmx)); +if (cpu_has_tertiary_exec_ctrls ()) { +vmx_compute_tertiary_exec_control (vmx); +tertiary_exec_controls_set (vmx, vmx->tertiary_exec_control); + }if (kvm_vcpu_apicv_active (&vmx->vcpu)) {vmcs_write64 (EOI_EXIT_BITMAP0 ,0 );
arch/x86/kvm/vmx/vmx.h +1 -0
@@ -209,6 +209,7 @@ struct vcpu_vmx {u32 msr_ia32_umwait_control;u32 secondary_exec_control; +u64 tertiary_exec_control;/* * loaded_vmcs points to the VMCS currently used in this vcpu. For a
Signature · 1 line
1.8.3.1
Sean Christopherson
maintainerRe: [RFC PATCH 08/12] kvm/vmx: Refactor vmx_compute_tertiary_exec_control()
Quoted 2 lines · Robert Hoo
Like
vmx_compute_tertiary_exec_control(), before L1 set VMCS, compute its nested VMX feature control MSR's value according to guest CPUID setting.
I haven't looked through this series in depth, but why is it refactoring code that it introduces in the same series? In other words, why not add the code that's needed right away?
Re: [RFC PATCH 08/12] kvm/vmx: Refactor vmx_compute_tertiary_exec_control()
Quoted 11 lines · Sean Christopherson
Quoted 4 lines · Robert Hoo
Like
vmx_compute_tertiary_exec_control(), before L1 set VMCS, compute its
nested VMX feature control MSR's value according to guest CPUID setting.I haven't looked through this series in depth, but why is it refactoring code
that it introduces in the same series? In other words, why not add the code
that's needed right away?
Yes, this will be corrected in next version.
RFC PATCH 9/12 kvm/vmx/vmcs12: Add Tertiary Exec-Control field in vmcs12
In reply to Robert Hoo--- arch/x86/kvm/vmx/vmcs12.c | 1 + arch/x86/kvm/vmx/vmcs12.h | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-)
arch/x86/kvm/vmx/vmcs12.c +1 -0
@@ -50,6 +50,7 @@FIELD64 (VMREAD_BITMAP , vmread_bitmap),FIELD64 (VMWRITE_BITMAP , vmwrite_bitmap),FIELD64 (XSS_EXIT_BITMAP , xss_exit_bitmap), +FIELD64 (TERTIARY_VM_EXEC_CONTROL , tertiary_vm_exec_control),FIELD64 (GUEST_PHYSICAL_ADDRESS , guest_physical_address),FIELD64 (VMCS_LINK_POINTER , vmcs_link_pointer), FIELD64(GUEST_IA32_DEBUGCTL, guest_ia32_debugctl),
arch/x86/kvm/vmx/vmcs12.h +2 -1
@@ -69,7 +69,8 @@ struct __packed vmcs12 {u64 vm_function_control;u64 eptp_list_address;u64 pml_address; -u64 padding64[3 ];/* room for future expansion */ +u64 tertiary_vm_exec_control; +u64 padding64[2 ];/* room for future expansion */ /* * To allow migration of L1 (complete with its L2 guests) between * machines of different natural widths (32 or 64 bit), we cannot have
Signature · 1 line
1.8.3.1
RFC PATCH 10/12 kvm/vmx/nested: Support tertiary VM-Exec control in vmcs02
In reply to Robert Hoo--- arch/x86/kvm/vmx/nested.c | 13 +++++++++++++ 1 file changed, 13 insertions(+)
arch/x86/kvm/vmx/nested.c +13 -0
@@ -2232,6 +2232,7 @@ static void prepare_vmcs02_early_rare(struct vcpu_vmx *vmx,static void prepare_vmcs02_early (struct vcpu_vmx *vmx,struct vmcs12 *vmcs12) {u32 exec_control, vmcs12_exec_ctrl; +u64 vmcs02_ter_exec_ctrl;u64 guest_efer =nested_vmx_calc_efer (vmx, vmcs12);if (vmx->nested.dirty_vmcs12 || vmx->nested.hv_evmcs)
@@ -2351,6 +2352,18 @@ static void prepare_vmcs02_early(struct vcpu_vmx *vmx, struct vmcs12 *vmcs12)vm_entry_controls_set (vmx, exec_control);/* +* Tertiary EXEC CONTROLS +*/ +if (cpu_has_tertiary_exec_ctrls ()) { + vmcs02_ter_exec_ctrl = vmx->tertiary_exec_control; +if (nested_cpu_has (vmcs12, +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS )) + vmcs02_ter_exec_ctrl |= vmcs12->tertiary_vm_exec_control; + +tertiary_exec_controls_set (vmx, vmcs02_ter_exec_ctrl); + } + +/* * EXIT CONTROLS * * L2->L1 exit controls are emulated - the hardware exit is to L0 so
Signature · 1 line
1.8.3.1
RFC PATCH 11/12 kvm/vmx/nested: Support CR4.KL in nested
In reply to Robert HooAdd CR4.KL in nested.msr.cr4_fixed1 when guest CPUID supports KeyLocker. So that it can pass check when preparing vmcs02.
--- arch/x86/kvm/vmx/vmx.c | 1 + 1 file changed, 1 insertion(+)
arch/x86/kvm/vmx/vmx.c +1 -0
@@ -7374,6 +7374,7 @@ static void nested_vmx_cr_fixed1_bits_update(struct kvm_vcpu *vcpu)cr4_fixed1_update (X86_CR4_PKE , ecx,feature_bit (PKU ));cr4_fixed1_update (X86_CR4_UMIP , ecx,feature_bit (UMIP ));cr4_fixed1_update (X86_CR4_LA57 , ecx,feature_bit (LA57 )); +cr4_fixed1_update (X86_CR4_KEYLOCKER , ecx,feature_bit (KEYLOCKER ));#undef cr4_fixed1_update }
Signature · 1 line
1.8.3.1
RFC PATCH 12/12 kvm/vmx/nested: Enable nested LOADIWKey VM-exit
In reply to Robert HooSet the LOADIWkey VM-exit bit in nested vmx ctrl MSR, and let L1 intercept L2's LOADIWKEY VM-Exit.
--- arch/x86/kvm/vmx/nested.c | 5 ++++- arch/x86/kvm/vmx/nested.h | 7 +++++++ 2 files changed, 11 insertions(+), 1 deletion(-)
arch/x86/kvm/vmx/nested.c +4 -1
@@ -5927,6 +5927,9 @@ static bool nested_vmx_l1_wants_exit(struct kvm_vcpu *vcpu, u32 exit_reason)case EXIT_REASON_TPAUSE :return nested_cpu_has2 (vmcs12,SECONDARY_EXEC_ENABLE_USR_WAIT_PAUSE ); +case EXIT_REASON_LOADIWKEY : +return nested_cpu_has3 (vmcs12, +TERTIARY_EXEC_LOADIWKEY_EXITING );default :return true; }
@@ -6441,7 +6444,7 @@ void nested_vmx_setup_ctls_msrs(struct nested_vmx_msrs *msrs, u32 ept_caps)if (msrs->procbased_ctls_high &CPU_BASED_ACTIVATE_TERTIARY_CONTROLS )rdmsrl (MSR_IA32_VMX_PROCBASED_CTLS3 , msrs->tertiary_ctls); - msrs->tertiary_ctls &= ~TERTIARY_EXEC_LOADIWKEY_EXITING ; + msrs->tertiary_ctls &=TERTIARY_EXEC_LOADIWKEY_EXITING ;/* * We can emulate "VMCS shadowing," even if the hardware * doesn't support it.
arch/x86/kvm/vmx/nested.h +7 -0
@@ -145,6 +145,13 @@ static inline bool nested_cpu_has2(struct vmcs12 *vmcs12, u32 bit) (vmcs12->secondary_vm_exec_control & bit); } +static inline bool nested_cpu_has3 (struct vmcs12 *vmcs12,u32 bit) +{ +return (vmcs12->cpu_based_vm_exec_control & +CPU_BASED_ACTIVATE_TERTIARY_CONTROLS ) && + (vmcs12->tertiary_vm_exec_control & bit); +} +static inline bool nested_cpu_has_preemption_timer (struct vmcs12 *vmcs12) { return vmcs12->pin_based_vm_exec_control &
Signature · 1 line
1.8.3.1
Sean Christopherson
maintainerQuoted 2 lines · Robert Hoo
IWKey, is the core of this framework. It is loaded into CPU by LOADIWKEY instruction, then inaccessible from (CPU) outside anymore.
Unless the VMM intercepts and saves the key in normal memory, which is what this series proposes to do. That needs to be called out very, very clearly.
Quoted 43 lines
LOADIWKEY is the
only Key Locker instruction that will cause VM-exit (if we set so in VM Execution Control). When load IWKey into CPU, we can ask CPU further randomize it, if HW supports this.
The IWKey can also be distributed among CPUs, rather than LOADIWKEY on each CPU, by: first backup IWKey to platform specific storage, then copy it on target CPU. The backup process is triggered by writing to MSRIA32_COPY_LOCAL_TO_PLATFORM. The restore process is triggered by writing to MSRIA32_COPY_PLATFORM_LOCAL.
Virtualization Design
Key Locker Spec [2] indicates virtualization limitations by current HW implementation.
1) IWKey cannot be read from CPU after it's loaded (this is the nature of this feature) and only 1 copy of IWKey inside 1 CPU.
2) Initial implementations may take a significant amount of time to perform a copy of IWKeyBackup to IWKey (via a write to MSRIA32_COPY_PLATFORM_LOCAL) so it may cause a significant performance impact to reload IWKey after each VM exit.
Due to above reasons, virtualization design makes below decisions
1) don't expose HW randomize IWKey capability (CPUID.0x19.ECX[1]) to guest. As such, guest IWKey cannot be preserved by VMM across VM-{Exit, Entry}. (VMM cannot know what exact IWKey were set by CPU)
2) guests and host can only use Key Locker feature exclusively. [4]The virtualization implementation is generally straight forward
1) On VM-Exit of guest 'LOADIWKEY', VMM stores the IWKey in vCPU scope area (kvm_vcpu_arch)
2) Right before VM-Entry, VMM load that vCPU's IWKey in to pCPU, by LOADIWKEY instruction.
3) On guest backup local to platform operation, VMM traps the write to MSR, and simulate the IWKey store process by store it in a KVM scope area (kvm_arch), mark the success status in the shadowmsr_ia32_iwkey_backup_statusandmsr_ia32_copy_status.
4) On guest copy from platform to local operation, VMM traps the write to MSR and simulate the process by load kvm_arch.iwkey_backup to vCPU.iwkey; and simulate the success status in the
shadowmsr_ia32_copy_status.
5) Guest read the 2 status MSRs will also be trapped and return the shadow value.
6) Other Key Locker instructions can run without VM-Exit in non-root mode.
Quoted 2 lines
At the end, we don't suggest this feature to be migratable, as if so, IWKey would have to be exposed to user space, which would weaken this feature's
/s/weaken/further weaken. Saving the key in host kernel memory already subverts IWKey to some extent.
Is there a concrete use case for virtualizing IWKey? The caveats that come with it quite nasty, e.g. reduced security (relative to native IWKey), not migratable, increased vCPU switching latency, etc...
Quoted 1 line
security significance.