From: Joel Fernandes <joel@joelfernandes.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
rostedt@goodmis.org, mingo@kernel.org,
gregkh@linuxfoundation.org, gustavo@embeddedor.com,
tglx@linutronix.de, paulmck@kernel.org, josh@joshtriplett.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com
Subject: Re: [PATCH v2 3/9] rcu,tracing: Create trace_rcu_{enter,exit}()
Date: Wed, 12 Feb 2020 18:20:05 -0500 [thread overview]
Message-ID: <20200212232005.GC115917@google.com> (raw)
In-Reply-To: <20200212210749.971717428@infradead.org>
On Wed, Feb 12, 2020 at 10:01:42PM +0100, Peter Zijlstra wrote:
> To facilitate tracers that need RCU, add some helpers to wrap the
> magic required.
>
> The problem is that we can call into tracers (trace events and
> function tracing) while RCU isn't watching and this can happen from
> any context, including NMI.
>
> It is this latter that is causing most of the trouble; we must make
> sure in_nmi() returns true before we land in anything tracing,
> otherwise we cannot recover.
>
> These helpers are macros because of header-hell; they're placed here
> because of the proximity to nmi_{enter,exit{().
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> include/linux/hardirq.h | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> --- a/include/linux/hardirq.h
> +++ b/include/linux/hardirq.h
> @@ -89,4 +89,52 @@ extern void irq_exit(void);
> arch_nmi_exit(); \
> } while (0)
>
> +/*
> + * Tracing vs RCU
> + * --------------
> + *
> + * tracepoints and function-tracing can happen when RCU isn't watching (idle,
> + * or early IRQ/NMI entry).
> + *
> + * When it happens during idle or early during IRQ entry, tracing will have
> + * to inform RCU that it ought to pay attention, this is done by calling
> + * rcu_irq_enter_irqsave().
> + *
> + * On NMI entry, we must be very careful that tracing only happens after we've
> + * incremented preempt_count(), otherwise we cannot tell we're in NMI and take
> + * the special path.
> + */
> +
> +#define __TR_IRQ 1
> +#define __TR_NMI 2
> +
> +#define trace_rcu_enter() \
> +({ \
> + unsigned long state = 0; \
> + if (!rcu_is_watching()) { \
> + if (in_nmi()) { \
> + state = __TR_NMI; \
> + rcu_nmi_enter(); \
> + } else { \
> + state = __TR_IRQ; \
> + rcu_irq_enter_irqsave(); \
I think this can be simplified. You don't need to rely on in_nmi() here. I
believe for NMI's, you can just call rcu_irq_enter_irqsave() and that should
be sufficient to get RCU watching. Paul can correct me if I'm wrong, but I am
pretty sure that would work.
In fact, I think a better naming for rcu_irq_enter_irqsave() pair could be
(in the first patch):
rcu_ensure_watching_begin();
rcu_ensure_watching_end();
thanks,
- Joel
> + } \
> + } \
> + state; \
> +})
> +
> +#define trace_rcu_exit(state) \
> +do { \
> + switch (state) { \
> + case __TR_IRQ: \
> + rcu_irq_exit_irqsave(); \
> + break; \
> + case __TR_NMI: \
> + rcu_nmi_exit(); \
> + break; \
> + default: \
> + break; \
> + } \
> +} while (0)
> +
> #endif /* LINUX_HARDIRQ_H */
>
>
next prev parent reply other threads:[~2020-02-12 23:20 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 21:01 [PATCH v2 0/9] tracing vs rcu vs nmi Peter Zijlstra
2020-02-12 21:01 ` [PATCH v2 1/9] rcu: Rename rcu_irq_{enter,exit}_irqson() Peter Zijlstra
2020-02-12 22:38 ` Joel Fernandes
2020-02-12 21:01 ` [PATCH v2 2/9] rcu: Mark rcu_dynticks_curr_cpu_in_eqs() inline Peter Zijlstra
2020-02-12 22:38 ` Joel Fernandes
2020-02-13 1:41 ` Steven Rostedt
2020-02-13 14:25 ` Joel Fernandes
2020-02-12 21:01 ` [PATCH v2 3/9] rcu,tracing: Create trace_rcu_{enter,exit}() Peter Zijlstra
2020-02-12 23:20 ` Joel Fernandes [this message]
2020-02-13 8:27 ` Peter Zijlstra
2020-02-13 13:31 ` Joel Fernandes
2020-02-13 13:51 ` Paul E. McKenney
2020-02-13 16:40 ` Peter Zijlstra
2020-02-13 18:56 ` Paul E. McKenney
2020-02-13 20:44 ` Joel Fernandes
2020-02-13 20:54 ` Paul E. McKenney
2020-02-13 21:19 ` Joel Fernandes
2020-02-13 21:38 ` Steven Rostedt
2020-02-13 21:50 ` Paul E. McKenney
2020-02-13 22:04 ` Steven Rostedt
2020-02-13 22:39 ` Paul E. McKenney
2020-02-14 6:19 ` Masami Hiramatsu
2020-02-15 14:59 ` Paul E. McKenney
2020-02-17 8:55 ` Masami Hiramatsu
2020-02-17 16:31 ` Paul E. McKenney
2020-02-18 4:33 ` Masami Hiramatsu
2020-02-18 16:12 ` Paul E. McKenney
2020-02-18 16:15 ` Mathieu Desnoyers
2020-02-18 16:35 ` Steven Rostedt
2020-02-18 17:46 ` Steven Rostedt
2020-02-18 20:18 ` Paul E. McKenney
2020-02-19 2:45 ` Masami Hiramatsu
2020-03-06 18:01 ` Masami Hiramatsu
2020-03-06 18:47 ` Joel Fernandes
2020-03-06 19:11 ` Joel Fernandes
2020-03-07 1:58 ` Masami Hiramatsu
2020-03-06 0:42 ` Thomas Gleixner
2020-02-13 21:48 ` Paul E. McKenney
2020-02-13 22:58 ` Joel Fernandes
2020-02-13 23:55 ` Steven Rostedt
2020-02-18 19:58 ` Peter Zijlstra
2020-02-18 20:17 ` Paul E. McKenney
2020-02-18 20:40 ` Peter Zijlstra
2020-02-18 21:39 ` Paul E. McKenney
2020-02-19 9:57 ` Peter Zijlstra
2020-02-19 12:46 ` Paul E. McKenney
2020-02-12 23:27 ` Joel Fernandes
2020-02-13 8:28 ` Peter Zijlstra
2020-02-13 18:39 ` Joel Fernandes
2020-02-12 21:01 ` [PATCH v2 4/9] sched,rcu,tracing: Avoid tracing before in_nmi() is correct Peter Zijlstra
2020-02-12 21:01 ` [PATCH v2 5/9] x86,tracing: Add comments to do_nmi() Peter Zijlstra
2020-02-12 21:01 ` [PATCH v2 6/9] perf,tracing: Prepare the perf-trace interface for RCU changes Peter Zijlstra
2020-02-12 23:28 ` Joel Fernandes
2020-02-13 8:29 ` Peter Zijlstra
2020-02-13 18:38 ` Joel Fernandes
2020-02-12 21:01 ` [PATCH v2 7/9] tracing: Employ trace_rcu_{enter,exit}() Peter Zijlstra
2020-02-12 21:01 ` [PATCH v2 8/9] tracing: Remove regular RCU context for _rcuidle tracepoints (again) Peter Zijlstra
2020-02-12 21:01 ` [PATCH v2 9/9] perf,tracing: Allow function tracing when !RCU Peter Zijlstra
2020-02-14 2:28 ` Sergey Senozhatsky
2020-02-14 2:42 ` Sergey Senozhatsky
2020-02-14 3:32 ` Steven Rostedt
2020-02-14 20:38 ` Kim Phillips
2020-02-14 22:48 ` Steven Rostedt
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=20200212232005.GC115917@google.com \
--to=joel@joelfernandes.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-arch@vger.kernel.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=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.