From: Joel Fernandes <joel@joelfernandes.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
rcu@vger.kernel.org
Subject: Re: [PATCH 3/8] srcu: Use local_lock() for per-CPU struct srcu_data access
Date: Wed, 20 May 2020 14:44:25 -0400 [thread overview]
Message-ID: <20200520184425.GA261674@google.com> (raw)
In-Reply-To: <20200520183529.GR317569@hirez.programming.kicks-ass.net>
On Wed, May 20, 2020 at 08:35:29PM +0200, Peter Zijlstra wrote:
> On Wed, May 20, 2020 at 08:28:00PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2020-05-20 13:42:59 [-0400], Joel Fernandes wrote:
> > > Hi Sebastian,
> > Hi Joel,
> >
> > > For pointer stability, can we just use get_local_ptr() and put_local_ptr()
> > > instead of adding an extra lock? This keeps the pointer stable while keeping
> > > the section preemptible on -rt. And we already have a lock in rcu_data, I
> > > prefer not to add another lock if possible.
> >
> > What is this get_local_ptr() doing? I can't find it anywhere…
>
> I suspect it is ({ preempt_disable(); this_cpu_ptr(ptr); }), or
> something along those lines.
>
> But yeah, I can't find it either.
I actually found it in RT 4.4 kernel, I thought this was also on newer RT
kernels as well (is that not true anymore?). But yes it was exactly what
Peter said.
In 4.4 RT there's code similar to:
#ifdef CONFIG_PREEMPT_RT_FULL
# define get_local_ptr(var) ({ \
migrate_disable(); \
this_cpu_ptr(var); })
# define put_local_ptr(var) do { \
(void)(var); \
migrate_enable(); \
} while (0)
#else
#define get_local_ptr(var) get_cpu_ptr(var)
#define put_local_ptr(var) put_cpu_ptr(var)
#endif
thanks,
- Joel
next prev parent reply other threads:[~2020-05-20 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200519201912.1564477-1-bigeasy@linutronix.de>
2020-05-19 20:19 ` [PATCH 3/8] srcu: Use local_lock() for per-CPU struct srcu_data access Sebastian Andrzej Siewior
2020-05-20 10:24 ` Peter Zijlstra
2020-05-20 12:06 ` Sebastian Andrzej Siewior
2020-05-20 13:27 ` Peter Zijlstra
2020-05-20 17:42 ` Joel Fernandes
2020-05-20 18:28 ` Sebastian Andrzej Siewior
2020-05-20 18:35 ` Peter Zijlstra
2020-05-20 18:44 ` Joel Fernandes [this message]
2020-05-20 18:50 ` Uladzislau Rezki
2020-05-20 18:59 ` Joel Fernandes
2020-05-20 18:43 ` Paul E. McKenney
2020-05-22 15:12 ` Sebastian Andrzej Siewior
2020-05-22 17:39 ` Paul E. McKenney
2020-05-23 15:08 ` Sebastian Andrzej Siewior
2020-05-23 16:59 ` Paul E. McKenney
2020-05-24 19:03 ` Sebastian Andrzej Siewior
2020-05-25 3:27 ` Paul E. McKenney
2020-05-26 13:41 ` [PATCH] srcu: Avoid local_irq_save() before acquiring spinlock_t Sebastian Andrzej Siewior
2020-05-26 16:16 ` Paul E. McKenney
2020-05-26 16:31 ` Sebastian Andrzej Siewior
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=20200520184425.GA261674@google.com \
--to=joel@joelfernandes.org \
--cc=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).