linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Juergen Gross <jgross@suse.com>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	mhocko@suse.com, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 3/3] kernel/smp: add more data to CSD lock debugging
Date: Fri, 26 Feb 2021 22:05:51 +0100	[thread overview]
Message-ID: <YDlirwTWMmZ3g0ts@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210226181205.GZ2743@paulmck-ThinkPad-P72>

On Fri, Feb 26, 2021 at 10:12:05AM -0800, Paul E. McKenney wrote:
> On Fri, Feb 26, 2021 at 05:38:44PM +0100, Peter Zijlstra wrote:
> > 
> > I hate all of this, but if this will finally catch the actual problem,
> > we can then revert all this, so sure.
> 
> OK, I will bite...  What exactly do you hate about it?

It's ugly and messy. We're basically commiting a debug session. Normally
gunk like this is done in private trees, then we find the problem and
fix that and crap like this never sees the light of day.

  reply	other threads:[~2021-02-26 21:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 11:25 [PATCH 0/3] kernel/smp.c: add more CSD lock debugging Juergen Gross
2021-02-26 11:25 ` [PATCH 1/3] kernel/smp: add boot parameter for controlling " Juergen Gross
2021-02-26 11:25 ` [PATCH 2/3] kernel/smp: prepare more " Juergen Gross
2021-02-26 11:25 ` [PATCH 3/3] kernel/smp: add more data to " Juergen Gross
2021-02-26 16:38   ` Peter Zijlstra
2021-02-26 18:12     ` Paul E. McKenney
2021-02-26 21:05       ` Peter Zijlstra [this message]
2021-03-01  0:07         ` Paul E. McKenney
2021-03-01 15:45           ` Peter Zijlstra
2021-03-01 15:53             ` Jürgen Groß
2021-03-01 16:45               ` 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=YDlirwTWMmZ3g0ts@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=corbet@lwn.net \
    --cc=jgross@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=paulmck@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;
as well as URLs for NNTP newsgroup(s).