KVM: VMX: don't use "unsigned long" in vmx_vcpu_enter_exit()
authorAlexey Dobriyan <adobriyan@gmail.com>
Fri, 18 Nov 2022 17:05:21 +0000 (20:05 +0300)
committerSean Christopherson <seanjc@google.com>
Tue, 24 Jan 2023 18:07:01 +0000 (10:07 -0800)
__vmx_vcpu_run_flags() returns "unsigned int" and uses only 2 bits of it
so using "unsigned long" is very much pointless.  Furthermore,
__vmx_vcpu_run() and vmx_spec_ctrl_restore_host() take an "unsigned int",
i.e. actually relying on an "unsigned long" value won't work.

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Reviewed-by: Sean Christopherson <seanjc@google.com>
Link: https://lore.kernel.org/r/Y3e7UW0WNV2AZmsZ@p183
Signed-off-by: Sean Christopherson <seanjc@google.com>
arch/x86/kvm/vmx/vmx.c

index c788aa3..506c324 100644 (file)
@@ -7172,7 +7172,7 @@ static fastpath_t vmx_exit_handlers_fastpath(struct kvm_vcpu *vcpu)
 
 static noinstr void vmx_vcpu_enter_exit(struct kvm_vcpu *vcpu,
                                        struct vcpu_vmx *vmx,
-                                       unsigned long flags)
+                                       unsigned int flags)
 {
        guest_state_enter_irqoff();