On Wed, Jan 04, 2023, Paul E. McKenney wrote: > Now that the SRCU Kconfig option is unconditionally selected, there is > no longer any point in selecting it. Therefore, remove the "select SRCU" > Kconfig statements. > > Signed-off-by: Paul E. McKenney <paulmck@xxxxxxxxxx> > Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > Cc: Ingo Molnar <mingo@xxxxxxxxxx> > Cc: Borislav Petkov <bp@xxxxxxxxx> > Cc: Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx> > Cc: "H. Peter Anvin" <hpa@xxxxxxxxx> > Cc: Sean Christopherson <seanjc@xxxxxxxxxx> > Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx> > Cc: <x86@xxxxxxxxxx> > Cc: <kvm@xxxxxxxxxxxxxxx> > --- ... > diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig > index fbeaa9ddef598..9306d99585188 100644 > --- a/arch/x86/kvm/Kconfig > +++ b/arch/x86/kvm/Kconfig > @@ -46,7 +46,6 @@ config KVM > select KVM_XFER_TO_GUEST_WORK > select KVM_GENERIC_DIRTYLOG_READ_PROTECT > select KVM_VFIO > - select SRCU Would it be too much trouble to bundle all of the KVM changes into a single patch? The SRCU requirement is a generic KVM requirement that's handled in the arch Kconfigs purely because of KVM's somewhat roundabout Kconfig setup. > select INTERVAL_TREE > select HAVE_KVM_PM_NOTIFIER if PM > help > -- > 2.31.1.189.g2e36527f23 >
