[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250721105348.05312994@batman.local.home>
Date: Mon, 21 Jul 2025 10:53:48 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: rcu@...r.kernel.org, linux-kernel@...r.kernel.org, kernel-team@...a.com,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Sebastian Andrzej
Siewior <bigeasy@...utronix.de>
Subject: Re: [PATCH v2 1/4] srcu: Move rcu_is_watching() checks to
srcu_read_{,un}lock_fast()
On Fri, 18 Jul 2025 17:28:14 -0700
"Paul E. McKenney" <paulmck@...nel.org> wrote:
> The rcu_is_watching() warnings are currently in the SRCU-tree
> implementations of __srcu_read_lock_fast() and __srcu_read_unlock_fast().
> However, this makes it difficult to create _notrace variants of
> srcu_read_lock_fast() and srcu_read_unlock_fast(). This commit therefore
> moves these checks to srcu_read_lock_fast(), srcu_read_unlock_fast(),
> srcu_down_read_fast(), and srcu_up_read_fast().
>
Paul,
Can you please send new versions of a patch set as a separate thread?
It is really difficult to sort out what patch goes with what when they
are all in the same thread. Even in tree view.
-- Steve
Powered by blists - more mailing lists