public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Andreas Larsson <andreas@gaisler.com>,
	Waiman Long <llong@redhat.com>,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	Boqun Feng <boqun.feng@gmail.com>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Will Deacon <will@kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] sparc/pci: Make pci_poke_lock a raw_spinlock_t.
Date: Wed, 27 Nov 2024 17:53:56 +0100	[thread overview]
Message-ID: <20241127165356.hnkqmgcc@linutronix.de> (raw)
In-Reply-To: <4eb7bb8e-c2aa-4ce5-9f15-3086fccf4e46@roeck-us.net>

On 2024-11-27 08:02:50 [-0800], Guenter Roeck wrote:
> On 11/27/24 07:39, Andreas Larsson wrote:
> > Even though this is for sparc64, there is work being done looking into
> > enabling RT for sparc32. If the amount of fixes needed to keep
> > PROVE_RAW_LOCK_NESTING enabled is quite small at the moment I'd rather
> > see it enabled for sparc rather than risking it becoming worse in the
> > future.

Okay. So you seem to be in favour of fixing the sparc64 splats Guenter
reported?

> > I don't know what the situation is for other architectures that does not
> > support RT.
> > 
> 
> For my part I still don't understand why PROVE_RAW_LOCK_NESTING is no longer
> a configurable option, or in other words why it is mandated even for architectures
> not supporting RT. To me this means that I'll either have to disable PROVE_LOCKING
> for sparc or live with endless warning backtraces. The latter obscures real
> problems, so it is a no-go.

It is documented in Documentation/locking/locktypes.rst how the locks
should nest. It is just nobody enabled it on sparc64 and tested. The
option was meant temporary until the big read blocks are cleared.

> So, if people want to keep mandating PROVE_RAW_LOCK_NESTING together with
> PROVE_LOCKING for all architectures, I'll disable PROVE_LOCKING for sparc
> in my testing. NP, just let me know. I'll then do the same for other
> architectures not supporting RT if I hit the same problem there.

Waiman posted a patch to disable it on architectures that don't support
PREEMPT_RT. You could also post the patches you discussed. Andreas does
not seem to be against it (but then I don't know if he is a 32 or 64bit
guy). I did not year from other architectures so far.

> Guenter

Sebastian

  reply	other threads:[~2024-11-27 16:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 15:45 [PATCH 0/1] lockdep: Enable PROVE_RAW_LOCK_NESTING with PROVE_LOCKING Sebastian Andrzej Siewior
2024-10-09 15:45 ` [PATCH 1/1] " Sebastian Andrzej Siewior
2024-10-09 16:50   ` Waiman Long
2024-10-09 22:47     ` Boqun Feng
2024-10-22 21:53   ` [tip: locking/core] " tip-bot2 for Sebastian Andrzej Siewior
2024-11-23 16:27   ` [PATCH 1/1] " Guenter Roeck
2024-11-25  8:53     ` [PATCH] sparc/pci: Make pci_poke_lock a raw_spinlock_t Sebastian Andrzej Siewior
2024-11-25 17:01       ` Guenter Roeck
2024-11-25 17:43         ` Sebastian Andrzej Siewior
2024-11-25 17:59           ` Guenter Roeck
2024-11-25 18:12             ` Sebastian Andrzej Siewior
2024-11-25 19:23               ` Guenter Roeck
2024-11-25 19:33                 ` Waiman Long
2024-11-25 20:06                   ` Guenter Roeck
2024-11-25 20:23                     ` Guenter Roeck
2024-11-25 20:54                       ` Waiman Long
2024-11-25 21:25                         ` Guenter Roeck
2024-11-25 21:29                           ` Waiman Long
2024-11-25 21:54                             ` Guenter Roeck
2024-11-25 22:33                               ` Waiman Long
2024-11-26 11:20                         ` Sebastian Andrzej Siewior
2024-11-26 16:59                           ` Waiman Long
2024-11-27 15:39                             ` Andreas Larsson
2024-11-27 16:02                               ` Guenter Roeck
2024-11-27 16:53                                 ` Sebastian Andrzej Siewior [this message]
2024-11-27 17:44                                   ` Guenter Roeck
2024-11-27 23:47                                     ` Waiman Long
2024-11-28  0:08                                       ` Guenter Roeck
2024-11-28  0:31                                         ` Waiman Long
2024-11-28  1:17                                           ` Guenter Roeck
2024-11-28  1:55                                             ` Waiman Long

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=20241127165356.hnkqmgcc@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=andreas@gaisler.com \
    --cc=boqun.feng@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=llong@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=will@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