From: "Paul E. McKenney" <paulmck@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
mingo@kernel.org, joel@joelfernandes.org,
gregkh@linuxfoundation.org, gustavo@embeddedor.com,
tglx@linutronix.de, josh@joshtriplett.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
luto@kernel.org, tony.luck@intel.com, frederic@kernel.org,
dan.carpenter@oracle.com, mhiramat@kernel.org,
Marco Elver <elver@google.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 16/22] locking/atomics, kcsan: Add KCSAN instrumentation
Date: Wed, 19 Feb 2020 09:36:20 -0800 [thread overview]
Message-ID: <20200219173620.GI2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200219165455.GM18400@hirez.programming.kicks-ass.net>
On Wed, Feb 19, 2020 at 05:54:55PM +0100, Peter Zijlstra wrote:
> On Wed, Feb 19, 2020 at 08:50:20AM -0800, Paul E. McKenney wrote:
> > On Wed, Feb 19, 2020 at 05:03:18PM +0100, Peter Zijlstra wrote:
> > > On Wed, Feb 19, 2020 at 10:46:26AM -0500, Steven Rostedt wrote:
> > > > On Wed, 19 Feb 2020 15:47:40 +0100
> > > > Peter Zijlstra <peterz@infradead.org> wrote:
> > > >
> > > > > From: Marco Elver <elver@google.com>
> > > > >
> > > > > This adds KCSAN instrumentation to atomic-instrumented.h.
> > > > >
> > > > > Signed-off-by: Marco Elver <elver@google.com>
> > > > > Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> > > > > [peterz: removed the actual kcsan hooks]
> > > > > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > > > > Reviewed-by: Mark Rutland <mark.rutland@arm.com>
> > > > > ---
> > > > > include/asm-generic/atomic-instrumented.h | 390 +++++++++++++++---------------
> > > > > scripts/atomic/gen-atomic-instrumented.sh | 14 -
> > > > > 2 files changed, 212 insertions(+), 192 deletions(-)
> > > > >
> > > >
> > > >
> > > > Does this and the rest of the series depend on the previous patches in
> > > > the series? Or can this be a series on to itself (patches 16-22)?
> > >
> > > It can probably stand on its own, but it very much is related in so far
> > > that it's fallout from staring at all this nonsense.
> > >
> > > Without these the do_int3() can actually have accidental tracing before
> > > reaching it's nmi_enter().
> >
> > The original is already in -tip, so some merge magic will be required.
>
> Yes, So I don't strictly need this one, but I do need the two next
> patches adding __always_inline to everything. I figured it was easier to
> also pick this one (and butcher it) than to rebase everything.
>
> I didn't want to depend on the locking/kcsan tree, and if this goes in,
> we do have to do something 'funny' there. Maybe rebase, maybe put in a
> few kcsan stubs so the original patch at least compiles. We'll see :/
Fair enough!
Thanx, Paul
next prev parent reply other threads:[~2020-02-19 17:36 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:47 [PATCH v3 00/22] tracing vs world Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 01/22] hardirq/nmi: Allow nested nmi_enter() Peter Zijlstra
2020-02-19 15:31 ` Steven Rostedt
2020-02-19 16:56 ` Borislav Petkov
2020-02-19 17:07 ` Peter Zijlstra
2020-02-20 8:41 ` Will Deacon
2020-02-20 9:19 ` Marc Zyngier
2020-02-20 13:18 ` Petr Mladek
2020-02-19 14:47 ` [PATCH v3 02/22] x86,mce: Delete ist_begin_non_atomic() Peter Zijlstra
2020-02-19 17:13 ` Borislav Petkov
2020-02-19 17:21 ` Andy Lutomirski
2020-02-19 17:33 ` Peter Zijlstra
2020-02-19 22:12 ` Andy Lutomirski
2020-02-19 22:33 ` Luck, Tony
2020-02-19 22:48 ` Andy Lutomirski
2020-02-20 7:39 ` Peter Zijlstra
2020-02-19 17:42 ` Borislav Petkov
2020-02-19 17:46 ` Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 03/22] x86: Replace ist_enter() with nmi_enter() Peter Zijlstra
2020-02-20 10:54 ` Borislav Petkov
2020-02-20 12:11 ` Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 04/22] x86/doublefault: Make memmove() notrace/NOKPROBE Peter Zijlstra
2020-02-19 15:36 ` Steven Rostedt
2020-02-19 15:40 ` Peter Zijlstra
2020-02-19 15:55 ` Steven Rostedt
2020-02-19 15:57 ` Peter Zijlstra
2020-02-19 16:04 ` Peter Zijlstra
2020-02-19 16:12 ` Steven Rostedt
2020-02-19 16:27 ` Paul E. McKenney
2020-02-19 16:34 ` Peter Zijlstra
2020-02-19 16:46 ` Paul E. McKenney
2020-02-19 17:05 ` Steven Rostedt
2020-02-20 12:17 ` Borislav Petkov
2020-02-20 12:37 ` Peter Zijlstra
2020-02-19 15:47 ` Steven Rostedt
2020-02-19 14:47 ` [PATCH v3 05/22] rcu: Make RCU IRQ enter/exit functions rely on in_nmi() Peter Zijlstra
2020-02-19 16:31 ` Paul E. McKenney
2020-02-19 16:37 ` Peter Zijlstra
2020-02-19 16:45 ` Paul E. McKenney
2020-02-19 17:03 ` Peter Zijlstra
2020-02-19 17:42 ` Paul E. McKenney
2020-02-19 17:16 ` [PATCH] rcu/kprobes: Comment why rcu_nmi_enter() is marked NOKPROBE Steven Rostedt
2020-02-19 17:18 ` Joel Fernandes
2020-02-19 17:41 ` Paul E. McKenney
2020-02-20 5:54 ` Masami Hiramatsu
2020-02-19 14:47 ` [PATCH v3 06/22] rcu: Rename rcu_irq_{enter,exit}_irqson() Peter Zijlstra
2020-02-19 16:38 ` Paul E. McKenney
2020-02-19 14:47 ` [PATCH v3 07/22] rcu: Mark rcu_dynticks_curr_cpu_in_eqs() inline Peter Zijlstra
2020-02-19 16:39 ` Paul E. McKenney
2020-02-19 17:19 ` Steven Rostedt
2020-02-19 14:47 ` [PATCH v3 08/22] rcu,tracing: Create trace_rcu_{enter,exit}() Peter Zijlstra
2020-02-19 15:49 ` Steven Rostedt
2020-02-19 15:58 ` Peter Zijlstra
2020-02-19 16:15 ` Steven Rostedt
2020-02-19 16:35 ` Peter Zijlstra
2020-02-19 16:44 ` Paul E. McKenney
2020-02-20 10:34 ` Peter Zijlstra
2020-02-20 13:58 ` Paul E. McKenney
2020-02-19 14:47 ` [PATCH v3 09/22] sched,rcu,tracing: Avoid tracing before in_nmi() is correct Peter Zijlstra
2020-02-19 15:50 ` Steven Rostedt
2020-02-19 15:50 ` Steven Rostedt
2020-02-19 14:47 ` [PATCH v3 10/22] x86,tracing: Add comments to do_nmi() Peter Zijlstra
2020-02-19 15:51 ` Steven Rostedt
2020-02-19 14:47 ` [PATCH v3 11/22] perf,tracing: Prepare the perf-trace interface for RCU changes Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 12/22] tracing: Employ trace_rcu_{enter,exit}() Peter Zijlstra
2020-02-19 15:52 ` Steven Rostedt
2020-02-19 14:47 ` [PATCH v3 13/22] tracing: Remove regular RCU context for _rcuidle tracepoints (again) Peter Zijlstra
2020-02-19 15:53 ` Steven Rostedt
2020-02-19 16:43 ` Paul E. McKenney
2020-02-19 16:47 ` Peter Zijlstra
2020-02-19 17:05 ` Peter Zijlstra
2020-02-19 17:21 ` Steven Rostedt
2020-02-19 17:40 ` Paul E. McKenney
2020-02-19 18:00 ` Steven Rostedt
2020-02-19 19:05 ` Paul E. McKenney
2020-02-19 14:47 ` [PATCH v3 14/22] perf,tracing: Allow function tracing when !RCU Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 15/22] x86/int3: Ensure that poke_int3_handler() is not traced Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 16/22] locking/atomics, kcsan: Add KCSAN instrumentation Peter Zijlstra
2020-02-19 15:46 ` Steven Rostedt
2020-02-19 16:03 ` Peter Zijlstra
2020-02-19 16:50 ` Paul E. McKenney
2020-02-19 16:54 ` Peter Zijlstra
2020-02-19 17:36 ` Paul E. McKenney [this message]
2020-02-19 14:47 ` [PATCH v3 17/22] asm-generic/atomic: Use __always_inline for pure wrappers Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 18/22] asm-generic/atomic: Use __always_inline for fallback wrappers Peter Zijlstra
2020-02-19 16:55 ` Paul E. McKenney
2020-02-19 17:06 ` Peter Zijlstra
2020-02-19 17:35 ` Paul E. McKenney
2020-02-19 14:47 ` [PATCH v3 19/22] compiler: Simple READ/WRITE_ONCE() implementations Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 20/22] locking/atomics: Flip fallbacks and instrumentation Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 21/22] x86/int3: Avoid atomic instrumentation Peter Zijlstra
2020-02-19 14:47 ` [PATCH v3 22/22] x86/int3: Ensure that poke_int3_handler() is not sanitized Peter Zijlstra
2020-02-19 16:06 ` Dmitry Vyukov
2020-02-19 16:30 ` Peter Zijlstra
2020-02-19 16:51 ` Peter Zijlstra
2020-02-19 17:20 ` Peter Zijlstra
2020-02-20 10:37 ` Dmitry Vyukov
2020-02-20 12:06 ` Peter Zijlstra
2020-02-20 16:22 ` Dmitry Vyukov
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=20200219173620.GI2935@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@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: 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).