kernel_samsung_a53x/arch/x86/kvm/vmx/run_flags.h

/* SPDX-License-Identifier: GPL-2.0 */
#ifndef __KVM_X86_VMX_RUN_FLAGS_H
#define __KVM_X86_VMX_RUN_FLAGS_H

#define VMX_RUN_VMRESUME_SHIFT		0
#define VMX_RUN_SAVE_SPEC_CTRL_SHIFT	1

#define VMX_RUN_VMRESUME		BIT(VMX_RUN_VMRESUME_SHIFT)
#define VMX_RUN_SAVE_SPEC_CTRL		BIT(VMX_RUN_SAVE_SPEC_CTRL_SHIFT)

#endif /* __KVM_X86_VMX_RUN_FLAGS_H */
Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00			`/* SPDX-License-Identifier: GPL-2.0 */`
			`#ifndef __KVM_X86_VMX_RUN_FLAGS_H`
			`#define __KVM_X86_VMX_RUN_FLAGS_H`

KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH From: Sean Christopherson <seanjc@google.com> commit 706a189dcf74d3b3f955e9384785e726ed6c7c80 upstream. Use EFLAGS.CF instead of EFLAGS.ZF to track whether to use VMRESUME versus VMLAUNCH. Freeing up EFLAGS.ZF will allow doing VERW, which clobbers ZF, for MDS mitigations as late as possible without needing to duplicate VERW for both paths. [ pawan: resolved merge conflict in __vmx_vcpu_run in backport. ] Signed-off-by: Sean Christopherson <seanjc@google.com> Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Reviewed-by: Nikolay Borisov <nik.borisov@suse.com> Link: https://lore.kernel.org/all/20240213-delay-verw-v8-5-a6216d83edb7%40linux.intel.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2024-03-12 15:40:56 -07:00			`#define VMX_RUN_VMRESUME_SHIFT 0`
			`#define VMX_RUN_SAVE_SPEC_CTRL_SHIFT 1`

			`#define VMX_RUN_VMRESUME BIT(VMX_RUN_VMRESUME_SHIFT)`
			`#define VMX_RUN_SAVE_SPEC_CTRL BIT(VMX_RUN_SAVE_SPEC_CTRL_SHIFT)`
Import A536BXXU9EXDC 2024-06-15 16:02:09 -03:00
			`#endif /* __KVM_X86_VMX_RUN_FLAGS_H */`