On Fri, 15 Sep 2023 17:31:02 -0700 Sean Christopherson <seanjc@xxxxxxxxxx> wrote: > Now that nothing in s390 or architecture agnostic code consumes HAVE_KVM, > stop selecting it in s390. This is one of several steps towards deleting > HAVE_KVM from the common KVM Kconfig. > > Signed-off-by: Sean Christopherson <seanjc@xxxxxxxxxx> > --- > arch/s390/Kconfig | 1 - > arch/s390/kvm/Kconfig | 1 - > 2 files changed, 2 deletions(-) > > diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig > index ae29e4392664..8a5dca0036d9 100644 > --- a/arch/s390/Kconfig > +++ b/arch/s390/Kconfig > @@ -193,7 +193,6 @@ config S390 > select HAVE_KPROBES > select HAVE_KPROBES_ON_FTRACE > select HAVE_KRETPROBES > - select HAVE_KVM > select HAVE_LIVEPATCH > select HAVE_MEMBLOCK_PHYS_MAP > select HAVE_MOD_ARCH_SPECIFIC > diff --git a/arch/s390/kvm/Kconfig b/arch/s390/kvm/Kconfig > index 459d536116a6..9056cee72945 100644 > --- a/arch/s390/kvm/Kconfig > +++ b/arch/s390/kvm/Kconfig > @@ -19,7 +19,6 @@ if VIRTUALIZATION > config KVM > def_tristate y > prompt "Kernel-based Virtual Machine (KVM) support" > - depends on HAVE_KVM > select PREEMPT_NOTIFIERS > select HAVE_KVM_CPU_RELAX_INTERCEPT > select HAVE_KVM_VCPU_ASYNC_IOCTL it looks like we don't use HAVE_KVM on s390x Reviewed-by: Claudio Imbrenda <imbrenda@xxxxxxxxxxxxx>
