From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Frederic Weisbecker <frederic@kernel.org>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: Instrumentation and RCU
Date: Thu, 12 Mar 2020 14:53:39 +0100 [thread overview]
Message-ID: <20200312135339.GS12561@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <87pndk5tb4.fsf@nanos.tec.linutronix.de>
On Tue, Mar 10, 2020 at 12:43:27PM +0100, Thomas Gleixner wrote:
> That's why we want the sections and the annotation. If something calls
> out of a noinstr section into a regular text section and the call is not
> annotated at the call site, then objtool can complain and tell you. What
> Peter and I came up with looks like this:
>
> noinstr foo()
> do_protected(); <- Safe because in the noinstr section
>
> instr_begin(); <- Marks the begin of a safe region, ignored
> by objtool
>
> do_stuff(); <- All good
>
> instr_end(); <- End of the safe region. objtool starts
> looking again
>
> do_other_stuff(); <- Unsafe because do_other_stuff() is
> not protected
> and:
>
> noinstr do_protected()
> bar(); <- objtool will complain here
>
> See?
Find here:
https://lkml.kernel.org/r/20200312134107.700205216@infradead.org
next prev parent reply other threads:[~2020-03-12 13:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 17:02 Thomas Gleixner
2020-03-09 18:15 ` Steven Rostedt
2020-03-09 18:42 ` Joel Fernandes
2020-03-09 19:07 ` Steven Rostedt
2020-03-09 19:20 ` Mathieu Desnoyers
2020-03-16 15:02 ` Joel Fernandes
2020-03-09 18:59 ` Thomas Gleixner
2020-03-10 8:09 ` Masami Hiramatsu
2020-03-10 11:43 ` Thomas Gleixner
2020-03-10 15:31 ` Mathieu Desnoyers
2020-03-10 15:46 ` Steven Rostedt
2020-03-10 16:21 ` Mathieu Desnoyers
2020-03-11 0:18 ` Masami Hiramatsu
2020-03-11 0:37 ` Mathieu Desnoyers
2020-03-11 7:48 ` Masami Hiramatsu
2020-03-10 16:06 ` Masami Hiramatsu
2020-03-12 13:53 ` Peter Zijlstra [this message]
2020-03-10 15:24 ` Mathieu Desnoyers
2020-03-10 17:05 ` Daniel Thompson
2020-03-09 18:37 ` Mathieu Desnoyers
2020-03-09 18:44 ` Steven Rostedt
2020-03-09 18:52 ` Mathieu Desnoyers
2020-03-09 19:09 ` Steven Rostedt
2020-03-09 19:25 ` Mathieu Desnoyers
2020-03-09 19:52 ` Thomas Gleixner
2020-03-10 15:03 ` Mathieu Desnoyers
2020-03-10 16:48 ` Thomas Gleixner
2020-03-10 17:40 ` Mathieu Desnoyers
2020-03-10 18:31 ` Thomas Gleixner
2020-03-10 18:37 ` Mathieu Desnoyers
2020-03-10 1:40 ` Alexei Starovoitov
2020-03-10 8:02 ` Thomas Gleixner
2020-03-10 16:54 ` Paul E. McKenney
2020-03-17 17:56 ` Joel Fernandes
2020-03-09 20:18 ` Peter Zijlstra
2020-03-09 20:47 ` Paul E. McKenney
2020-03-09 20:58 ` Steven Rostedt
2020-03-09 21:25 ` Paul E. McKenney
2020-03-09 23:52 ` Frederic Weisbecker
2020-03-10 2:26 ` Paul E. McKenney
2020-03-10 15:13 ` Mathieu Desnoyers
2020-03-10 16:49 ` Paul E. McKenney
2020-03-10 17:22 ` Mathieu Desnoyers
2020-03-10 17:26 ` Paul E. McKenney
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=20200312135339.GS12561@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ast@kernel.org \
--cc=frederic@kernel.org \
--cc=jason.wessel@windriver.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome