Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 22 Mar 2023 10:57:19 +0100
From:   Peter Zijlstra <peterz@infradead.org>
To:     "Paul E. McKenney" <paulmck@kernel.org>
Cc:     linux-kernel@vger.kernel.org, kernel-team@meta.com,
        rostedt@goodmis.org, jgross@suse.com, mingo@kernel.org,
        corbet@lwn.net, vschneid@redhat.com
Subject: Re: [PATCH RFC smp] Remove diagnostics and adjust config for CSD
 lock diagnostics
Message-ID: <20230322095719.GT2017917@hirez.programming.kicks-ass.net>
References: <0c368b66-71b2-442f-a8f7-e6decc4be2d6@paulmck-laptop>
 <20230321102220.GH2234901@hirez.programming.kicks-ass.net>
 <1b48795e-8ec7-4628-b926-38f21a024a9d@paulmck-laptop>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1b48795e-8ec7-4628-b926-38f21a024a9d@paulmck-laptop>
Precedence: bulk

On Tue, Mar 21, 2023 at 08:38:50AM -0700, Paul E. McKenney wrote:
> On Tue, Mar 21, 2023 at 11:22:20AM +0100, Peter Zijlstra wrote:
> > On Mon, Mar 20, 2023 at 05:54:39PM -0700, Paul E. McKenney wrote:
> > > Hello!
> > > 
> > > This series removes CSD-lock diagnostics that were once very useful
> > > but which have not seen much action since.  It also adjusts Kconfig and
> > > kernel-boot-parameter setup.
> > > 
> > > 1.	locking/csd_lock: Add Kconfig option for csd_debug default.
> > > 
> > > 2.	locking/csd_lock: Remove added data from CSD lock debugging.
> > > 
> > > 3.	locking/csd_lock: Remove per-CPU data indirection from CSD
> > > 	lock debugging.
> > > 
> > > 4.	kernel/smp: Make csdlock_debug= resettable.
> > > 
> > > 						Thanx, Paul
> > > 
> > > ------------------------------------------------------------------------
> > > 
> > >  Documentation/admin-guide/kernel-parameters.txt   |   17 -
> > >  b/Documentation/admin-guide/kernel-parameters.txt |    6 
> > >  b/kernel/smp.c                                    |    2 
> > >  b/lib/Kconfig.debug                               |    9 
> > >  kernel/smp.c                                      |  260 ++--------------------
> > >  5 files changed, 47 insertions(+), 247 deletions(-)
> > 
> > Yay!! How do you want to route these, should I take them through tip?
> 
> Either way works for me.  If you take them into -tip, I will drop them
> from -rcu.  If you don't take them into -tip, I will send Linus a pull
> request for the upcoming merge window.  And if you take them at just
> the wrong time, we will both send them to Linus.  ;-)
> 
> Your choice!

OK, since they conflict a wee bit with Valentin's IPI tracepoint stuff,
I'm probably going to take both these series, let me stomp on the
conflict and feed it to the robots to see how bad it all gets :-)

I'll let you know if/when i'll push them to -tip.