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
Subject: Re: [PATCH RFC smp] Remove diagnostics and adjust config for CSD lock diagnostics
Date: Tue, 21 Mar 2023 11:22:20 +0100 [thread overview]
Message-ID: <20230321102220.GH2234901@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <0c368b66-71b2-442f-a8f7-e6decc4be2d6@paulmck-laptop>
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?
What about the rest of the thing? Your commits seem to suggest it's
still actually used -- why? Are there still more virt bugs?
next prev parent reply other threads:[~2023-03-21 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 0:54 Paul E. McKenney
2023-03-21 0:55 ` [PATCH CSDlock 1/4] locking/csd_lock: Add Kconfig option for csd_debug default Paul E. McKenney
2023-03-28 8:34 ` [tip: smp/core] " tip-bot2 for Paul E. McKenney
2023-03-21 0:55 ` [PATCH CSDlock 2/4] locking/csd_lock: Remove added data from CSD lock debugging Paul E. McKenney
2023-03-28 8:34 ` [tip: smp/core] " tip-bot2 for Paul E. McKenney
2023-03-21 0:55 ` [PATCH CSDlock 3/4] locking/csd_lock: Remove per-CPU data indirection " Paul E. McKenney
2023-03-28 8:34 ` [tip: smp/core] " tip-bot2 for Paul E. McKenney
2023-03-21 0:55 ` [PATCH CSDlock 4/4] kernel/smp: Make csdlock_debug= resettable Paul E. McKenney
2023-03-28 8:34 ` [tip: smp/core] " tip-bot2 for Paul E. McKenney
2023-03-28 18:16 ` Paul E. McKenney
2023-03-21 5:46 ` [PATCH RFC smp] Remove diagnostics and adjust config for CSD lock diagnostics Juergen Gross
2023-03-21 10:22 ` Peter Zijlstra [this message]
2023-03-21 15:38 ` Paul E. McKenney
2023-03-22 9:57 ` Peter Zijlstra
2023-03-22 14:46 ` 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=20230321102220.GH2234901@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=corbet@lwn.net \
--cc=jgross@suse.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®