linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Fernandes <joelagnelf@nvidia.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, rostedt@goodmis.org,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH v3 3/4] srcu: Add guards for notrace variants of SRCU-fast readers
Date: Tue, 22 Jul 2025 18:16:25 -0400	[thread overview]
Message-ID: <20250722221625.GA377653@joelbox2> (raw)
In-Reply-To: <20250721162433.10454-3-paulmck@kernel.org>

On Mon, Jul 21, 2025 at 09:24:32AM -0700, Paul E. McKenney wrote:
> This adds the usual scoped_guard(srcu_fast_notrace, &my_srcu) and
> guard(srcu_fast_notrace)(&my_srcu).
> 
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>

Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>

thanks,

 - Joel

> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>  include/linux/srcu.h | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/include/linux/srcu.h b/include/linux/srcu.h
> index 7a692bf8f99b9..ada65b58bc4c5 100644
> --- a/include/linux/srcu.h
> +++ b/include/linux/srcu.h
> @@ -515,4 +515,9 @@ DEFINE_LOCK_GUARD_1(srcu_fast, struct srcu_struct,
>  		    srcu_read_unlock_fast(_T->lock, _T->scp),
>  		    struct srcu_ctr __percpu *scp)
>  
> +DEFINE_LOCK_GUARD_1(srcu_fast_notrace, struct srcu_struct,
> +		    _T->scp = srcu_read_lock_fast_notrace(_T->lock),
> +		    srcu_read_unlock_fast_notrace(_T->lock, _T->scp),
> +		    struct srcu_ctr __percpu *scp)
> +
>  #endif
> -- 
> 2.40.1
> 

  reply	other threads:[~2025-07-22 22:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 16:24 [PATCH v3 0/4] Switch __DECLARE_TRACE() to notrace variant of SRCU-fast Paul E. McKenney
2025-07-21 16:24 ` [PATCH v3 1/4] srcu: Move rcu_is_watching() checks to srcu_read_{,un}lock_fast() Paul E. McKenney
2025-07-22 22:04   ` Joel Fernandes
2025-07-21 16:24 ` [PATCH v3 2/4] srcu: Add srcu_read_lock_fast_notrace() and srcu_read_unlock_fast_notrace() Paul E. McKenney
2025-07-22 22:11   ` Joel Fernandes
2025-07-22 22:34     ` Paul E. McKenney
2025-07-22 22:47       ` Steven Rostedt
2025-07-22 22:51         ` Paul E. McKenney
2025-07-23 15:23       ` Mathieu Desnoyers
2025-07-23 16:28         ` Paul E. McKenney
2025-07-21 16:24 ` [PATCH v3 3/4] srcu: Add guards for notrace variants of SRCU-fast readers Paul E. McKenney
2025-07-22 22:16   ` Joel Fernandes [this message]
2025-07-21 16:24 ` [PATCH v3 4/4] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE_CALL() with SRCU-fast Paul E. McKenney
2025-07-22 22:16 ` [PATCH v3 5/4] srcu: Document __srcu_read_{,un}lock_fast() implicit RCU readers Paul E. McKenney
2025-07-23 13:32   ` Joel Fernandes
2025-07-23 16:10     ` Joel Fernandes
2025-07-23 16:24       ` Paul E. McKenney
2025-07-22 22:17 ` [PATCH v3 6/4] srcu: Document srcu_flip() memory-barrier D relation to SRCU-fast 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=20250722221625.GA377653@joelbox2 \
    --to=joelagnelf@nvidia.com \
    --cc=bigeasy@linutronix.de \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.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;
as well as URLs for NNTP newsgroup(s).