Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/x86.c
between commit:
3eaa50e1e255e ("x86/cpu: Hide and rename static_cpu_has()")
from the tip tree and commit:
7a26830801584 ("KVM: x86: Move the bulk of MSR specific code from x86.c to msrs.{c,h}")
from the kvm tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc arch/x86/kvm/x86.c
index 63daa4dfa23ad,0626e835e9eb7..0000000000000
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
diff --git a/arch/x86/kvm/msrs.c b/arch/x86/kvm/msrs.c
index c230b18d87e38..861d04bfa63dd 100644
--- a/arch/x86/kvm/msrs.c
+++ b/arch/x86/kvm/msrs.c
@@ -651,7 +651,7 @@ static int set_efer(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
if ((efer ^ old_efer) & KVM_MMU_EFER_ROLE_BITS)
kvm_mmu_reset_context(vcpu);
- if (!static_cpu_has(X86_FEATURE_XSAVES) &&
+ if (!cpu_feature_enabled(X86_FEATURE_XSAVES) &&
(efer & EFER_SVME))
kvm_hv_xsaves_xsavec_maybe_warn(vcpu);
On July 8, 2026 2:59:07 PM UTC, Mark Brown <broonie@kernel.org> wrote: >diff --cc arch/x86/kvm/x86.c >index 63daa4dfa23ad,0626e835e9eb7..0000000000000 >--- a/arch/x86/kvm/x86.c >+++ b/arch/x86/kvm/x86.c >diff --git a/arch/x86/kvm/msrs.c b/arch/x86/kvm/msrs.c >index c230b18d87e38..861d04bfa63dd 100644 >--- a/arch/x86/kvm/msrs.c >+++ b/arch/x86/kvm/msrs.c >@@ -651,7 +651,7 @@ static int set_efer(struct kvm_vcpu *vcpu, struct msr_data *msr_info) > if ((efer ^ old_efer) & KVM_MMU_EFER_ROLE_BITS) > kvm_mmu_reset_context(vcpu); > >- if (!static_cpu_has(X86_FEATURE_XSAVES) && >+ if (!cpu_feature_enabled(X86_FEATURE_XSAVES) && > (efer & EFER_SVME)) > kvm_hv_xsaves_xsavec_maybe_warn(vcpu); Yap, LGTM. Thx. -- Small device. Typos and formatting crap
© 2016 - 2026 Red Hat, Inc.