From: Sean Christopherson <seanjc@google.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Paolo Bonzini <pbonzini@redhat.com>,
x86@kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH rcu 01/27] arch/x86: Remove "select SRCU"
Date: Tue, 10 Jan 2023 19:55:13 +0000 [thread overview]
Message-ID: <Y73CoUO63TOxmmnC@google.com> (raw)
In-Reply-To: <20230109200553.GA4154229@paulmck-ThinkPad-P17-Gen-1>
On Mon, Jan 09, 2023, Paul E. McKenney wrote:
> On Mon, Jan 09, 2023 at 11:22:28AM -0800, Paul E. McKenney wrote:
> > On Mon, Jan 09, 2023 at 05:43:23PM +0000, Sean Christopherson wrote:
> > > 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@kernel.org>
> > > > Cc: Thomas Gleixner <tglx@linutronix.de>
> > > > Cc: Ingo Molnar <mingo@redhat.com>
> > > > Cc: Borislav Petkov <bp@alien8.de>
> > > > Cc: Dave Hansen <dave.hansen@linux.intel.com>
> > > > Cc: "H. Peter Anvin" <hpa@zytor.com>
> > > > Cc: Sean Christopherson <seanjc@google.com>
> > > > Cc: Paolo Bonzini <pbonzini@redhat.com>
> > > > Cc: <x86@kernel.org>
> > > > Cc: <kvm@vger.kernel.org>
> > > > ---
> > >
> > > ...
> > >
> > > > 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.
> >
> > No problem, and will do on my next rebase. I might end up with a long
> > list of Cc's, but so it goes. I will of course send the result as a
> > reply to this message.
>
> Like this?
Ya, looks good!
next prev parent reply other threads:[~2023-01-10 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230105003759.GA1769545@paulmck-ThinkPad-P17-Gen-1>
2023-01-05 0:37 ` [PATCH rcu 01/27] arch/x86: Remove "select SRCU" Paul E. McKenney
2023-01-09 17:43 ` Sean Christopherson
2023-01-09 19:22 ` Paul E. McKenney
2023-01-09 20:05 ` Paul E. McKenney
2023-01-10 19:55 ` Sean Christopherson [this message]
2023-01-12 0:05 ` Paul E. McKenney
2023-01-05 0:37 ` [PATCH rcu 03/27] arch/mips/kvm: " Paul E. McKenney
2023-01-05 0:37 ` [PATCH rcu 05/27] arch/riscv/kvm: " Paul E. McKenney
2023-01-07 9:58 ` Anup Patel
2023-01-07 16:03 ` Paul E. McKenney
2023-01-05 0:37 ` [PATCH rcu 06/27] arch/s390/kvm: " Paul E. McKenney
2023-01-05 8:06 ` Heiko Carstens
2023-01-05 15:30 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y73CoUO63TOxmmnC@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox