[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240823185323.2563194-1-jmattson@google.com>
Date: Fri, 23 Aug 2024 11:53:09 -0700
From: Jim Mattson <jmattson@...gle.com>
To: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, Josh Poimboeuf <jpoimboe@...nel.org>,
Jim Mattson <jmattson@...gle.com>, Sandipan Das <sandipan.das@....com>,
Kai Huang <kai.huang@...el.com>, x86@...nel.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Subject: [PATCH v3 0/4] Distinguish between variants of IBPB
Prior to Zen4, AMD's IBPB did not flush the RAS (or, in Intel
terminology, the RSB). Hence, the older version of AMD's IBPB was not
equivalent to Intel's IBPB. However, KVM has been treating them as
equivalent, synthesizing Intel's CPUID.(EAX=7,ECX=0):EDX[bit 26] on any
platform that supports the synthetic features X86_FEATURE_IBPB and
X86_FEATURE_IBRS.
Equivalence also requires a previously ignored feature on the AMD side,
CPUID Fn8000_0008_EBX[IBPB_RET], which is enumerated on Zen4.
v3: Pass through IBPB_RET from hardware to userspace. [Tom]
Derive AMD_IBPB from X86_FEATURE_SPEC_CTRL rather than
X86_FEATURE_IBPB. [Tom]
Clarify semantics of X86_FEATURE_IBPB.
v2: Use IBPB_RET to identify semantic equality. [Venkatesh]
Jim Mattson (4):
x86/cpufeatures: Clarify semantics of X86_FEATURE_IBPB
x86/cpufeatures: Define X86_FEATURE_AMD_IBPB_RET
KVM: x86: Advertise AMD_IBPB_RET to userspace
KVM: x86: AMD's IBPB is not equivalent to Intel's IBPB
arch/x86/include/asm/cpufeatures.h | 3 ++-
arch/x86/kvm/cpuid.c | 8 ++++++--
2 files changed, 8 insertions(+), 3 deletions(-)
--
2.46.0.295.g3b9ea8a38a-goog
Powered by blists - more mailing lists