While putting together another patch modifying the secondary exec
controls I noticed that vmx_vcpu_update_vmfunc_ve() does a raw VMWRITE
instead of going through the designated function. I assume that is not
how it should be.
Signed-off-by: Jan Beulich <jbeul...@suse.com>
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -2062,9 +2062,7 @@ static void vmx_vcpu_update_vmfunc_ve(st
else
v->arch.hvm_vmx.secondary_exec_control &= ~mask;
- __vmwrite(SECONDARY_VM_EXEC_CONTROL,
- v->arch.hvm_vmx.secondary_exec_control);
-
+ vmx_update_secondary_exec_control(v);
vmx_vmcs_exit(v);
}
VMX: don't bypass vmx_update_secondary_exec_control()
While putting together another patch modifying the secondary exec
controls I noticed that vmx_vcpu_update_vmfunc_ve() does a raw VMWRITE
instead of going through the designated function. I assume that is not
how it should be.
Signed-off-by: Jan Beulich <jbeul...@suse.com>
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -2062,9 +2062,7 @@ static void vmx_vcpu_update_vmfunc_ve(st
else
v->arch.hvm_vmx.secondary_exec_control &= ~mask;
- __vmwrite(SECONDARY_VM_EXEC_CONTROL,
- v->arch.hvm_vmx.secondary_exec_control);
-
+ vmx_update_secondary_exec_control(v);
vmx_vmcs_exit(v);
}
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
