From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: John Stultz <john.stultz@linaro.org>,
paulmck@kernel.org, Josh Triplett <josh@joshtriplett.org>,
lkml <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Saravana Kannan <saravanak@google.com>,
Todd Kjos <tkjos@google.com>, Stephen Boyd <sboyd@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: On trace_*_rcuidle functions in modules
Date: Thu, 16 Apr 2020 00:40:56 +0200 [thread overview]
Message-ID: <20200415224056.GO2483@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20200415161424.584d07d3@gandalf.local.home>
On Wed, Apr 15, 2020 at 04:14:24PM -0400, Steven Rostedt wrote:
> Which was added because the rcuidle variant called RCU code that was not
> exported either. Which would have the same issue now as
> rcu_irq_exit_irqson() is also not exported. Which would be needed.
Keeping all RCU_NONIDLE code in the core kernel allows us to eventually
clean it all up. Allowing it to escape into modules makes that ever so
much harder :/
prev parent reply other threads:[~2020-04-15 22:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 2:20 On trace_*_rcuidle functions in modules John Stultz
2020-04-15 2:57 ` Paul E. McKenney
2020-04-15 3:47 ` John Stultz
2020-04-15 13:12 ` Paul E. McKenney
2020-04-15 12:53 ` Steven Rostedt
2020-04-15 19:56 ` John Stultz
2020-04-15 20:14 ` Steven Rostedt
2020-04-15 20:17 ` John Stultz
2020-04-15 20:41 ` Steven Rostedt
2020-04-15 21:02 ` John Stultz
2020-04-15 21:49 ` Steven Rostedt
2020-04-15 22:04 ` Paul E. McKenney
2020-04-15 22:42 ` Peter Zijlstra
2020-04-15 22:53 ` Steven Rostedt
2020-04-15 22:53 ` Paul E. McKenney
2020-04-15 22:51 ` Steven Rostedt
2020-04-15 22:54 ` Paul E. McKenney
2020-04-16 0:06 ` John Stultz
2020-04-16 0:48 ` Steven Rostedt
2020-04-16 1:02 ` Bjorn Andersson
2020-04-16 1:24 ` Steven Rostedt
2020-04-16 2:17 ` John Stultz
2020-04-15 22:07 ` John Stultz
2020-04-15 22:40 ` Peter Zijlstra [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=20200415224056.GO2483@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bjorn.andersson@linaro.org \
--cc=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=tkjos@google.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 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.