LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> To: Steven Rostedt <rostedt@goodmis.org> Cc: Joel Fernandes <joelaf@google.com>, LKML <linux-kernel@vger.kernel.org>, Peter Zilstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Tom Zanussi <tom.zanussi@linux.intel.com>, Namhyung Kim <namhyung@kernel.org>, Thomas Glexiner <tglx@linutronix.de>, Boqun Feng <boqun.feng@gmail.com>, Frederic Weisbecker <fweisbec@gmail.com>, Randy Dunlap <rdunlap@infradead.org>, Masami Hiramatsu <mhiramat@kernel.org>, Fenguang Wu <fengguang.wu@intel.com>, Baohong Liu <baohong.liu@intel.com>, Vedang Patel <vedang.patel@intel.com>, "Cc: Android Kernel" <kernel-team@android.com> Subject: Re: [PATCH RFC] tracepoint: Introduce tracepoint callbacks executing with preempt on Date: Fri, 27 Apr 2018 10:05:17 -0700 [thread overview] Message-ID: <20180427170517.GA799@linux.vnet.ibm.com> (raw) In-Reply-To: <20180427170048.GP26088@linux.vnet.ibm.com> On Fri, Apr 27, 2018 at 10:00:48AM -0700, Paul E. McKenney wrote: > On Fri, Apr 27, 2018 at 12:46:41PM -0400, Steven Rostedt wrote: > > On Fri, 27 Apr 2018 09:45:54 -0700 > > "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote: > > > > > > > That shouldn't be needed. For the rcu_read_lock_sched case, there is a > > > > > preempt_disable which needs to be a notrace, but for the srcu one, > > > > > since we don't do that, I think it should be fine. > > > > > > > > Actually, I think I may agree here too. Because the _notrace is for > > > > function tracing, and it shouldn't affect it. If people don't want it > > > > traced, they could add those functions to the list in the notrace file. > > > > > > OK, feel free to ignore my notrace srcu_read_lock() patch, then. ;-) > > > > Of course I wasn't thinking about the lockdep tracepoints that Joel > > mentioned, which happens to be the reason for all this discussion in > > the first place :-) Now I think we do need it. (OK, I can keep > > changing my mind, can't I?). > > You can, but at some point I start applying heavy-duty hysteresis. ;-) > > So the current thought (as of your having sent the above email) is that > we need notrace versions of srcu_read_lock() and srcu_read_unlock(), > but not for __srcu_read_lock() and __srcu_read_unlock(), correct? And Joel noted offline that I messed up srcu_read_unlock_notrace(), so here is an updated patch with that fixed. Thanx, Paul ------------------------------------------------------------------------ diff --git a/include/linux/srcu.h b/include/linux/srcu.h index 91494d7e8e41..3e72a291c401 100644 --- a/include/linux/srcu.h +++ b/include/linux/srcu.h @@ -195,6 +195,16 @@ static inline int srcu_read_lock(struct srcu_struct *sp) __acquires(sp) return retval; } +/* Used by tracing, cannot be traced and cannot invoke lockdep. */ +static inline notrace int +srcu_read_lock_notrace(struct srcu_struct *sp) __acquires(sp) +{ + int retval; + + retval = __srcu_read_lock(sp); + return retval; +} + /** * srcu_read_unlock - unregister a old reader from an SRCU-protected structure. * @sp: srcu_struct in which to unregister the old reader. @@ -209,6 +219,13 @@ static inline void srcu_read_unlock(struct srcu_struct *sp, int idx) __srcu_read_unlock(sp, idx); } +/* Used by tracing, cannot be traced and cannot call lockdep. */ +static inline notrace void +srcu_read_unlock_notrace(struct srcu_struct *sp, int idx) __releases(sp) +{ + __srcu_read_unlock(sp, idx); +} + /** * smp_mb__after_srcu_read_unlock - ensure full ordering after srcu_read_unlock *
prev parent reply other threads:[~2018-04-27 17:04 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-27 4:26 [PATCH RFC] tracepoint: Introduce tracepoint callbacks executing with preempt on Joel Fernandes 2018-04-27 14:26 ` Mathieu Desnoyers 2018-04-27 14:47 ` Steven Rostedt 2018-04-27 15:38 ` Paul E. McKenney 2018-04-27 15:40 ` Steven Rostedt 2018-04-27 15:43 ` Mathieu Desnoyers 2018-04-27 16:08 ` Steven Rostedt 2018-04-27 15:58 ` Paul E. McKenney 2018-04-27 15:42 ` Mathieu Desnoyers 2018-04-27 16:07 ` Steven Rostedt 2018-04-27 16:30 ` Joel Fernandes 2018-04-27 16:37 ` Steven Rostedt 2018-04-27 18:11 ` Joel Fernandes 2018-04-27 18:42 ` Mathieu Desnoyers 2018-04-27 15:57 ` Paul E. McKenney 2018-04-27 16:13 ` Steven Rostedt 2018-04-27 16:22 ` Joel Fernandes 2018-04-27 16:44 ` Paul E. McKenney 2018-04-27 16:14 ` Joel Fernandes 2018-04-27 16:22 ` Steven Rostedt 2018-04-27 16:45 ` Paul E. McKenney 2018-04-27 16:46 ` Steven Rostedt 2018-04-27 17:00 ` Paul E. McKenney 2018-04-27 17:05 ` Paul E. McKenney [this message]
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=20180427170517.GA799@linux.vnet.ibm.com \ --to=paulmck@linux.vnet.ibm.com \ --cc=baohong.liu@intel.com \ --cc=boqun.feng@gmail.com \ --cc=fengguang.wu@intel.com \ --cc=fweisbec@gmail.com \ --cc=joelaf@google.com \ --cc=kernel-team@android.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mathieu.desnoyers@efficios.com \ --cc=mhiramat@kernel.org \ --cc=mingo@redhat.com \ --cc=namhyung@kernel.org \ --cc=peterz@infradead.org \ --cc=rdunlap@infradead.org \ --cc=rostedt@goodmis.org \ --cc=tglx@linutronix.de \ --cc=tom.zanussi@linux.intel.com \ --cc=vedang.patel@intel.com \ /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: linkBe 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).