From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC][PATCH] tracepoints: Free early tracepoints after RCU is initialized
Date: Fri, 10 Aug 2018 10:07:09 -0700 [thread overview]
Message-ID: <20180810170709.GW24813@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180810123517.5e9714ad@gandalf.local.home>
On Fri, Aug 10, 2018 at 12:35:17PM -0400, Steven Rostedt wrote:
> On Fri, 10 Aug 2018 12:30:42 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Maybe I should say SRCU?
That would be an improvement. What, me read comments? ;-)
Thanx, Paul
> +/* SRCU is initialized at core_initcall */
> +postcore_initcall(release_early_probes);
> +
> static inline void release_probes(struct tracepoint_func *old)
> {
> if (old) {
> struct tp_probes *tp_probes = container_of(old,
> struct tp_probes, probes[0]);
> +
> + /*
> + * We can't free probes if SRCU is not initialized yet.
> + * Postpone the freeing till after SRCU is initialized.
> + */
> + if (unlikely(!ok_to_free_tracepoints)) {
> + tp_probes->rcu.next = early_probes;
> + early_probes = &tp_probes->rcu;
> + return;
> + }
> +
>
> -- Steve
>
next prev parent reply other threads:[~2018-08-10 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 16:30 [RFC][PATCH] tracepoints: Free early tracepoints after RCU is initialized Steven Rostedt
2018-08-10 16:35 ` Steven Rostedt
2018-08-10 17:07 ` Paul E. McKenney [this message]
2018-08-10 17:06 ` Paul E. McKenney
2018-08-10 17:11 ` Joel Fernandes
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=20180810170709.GW24813@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.