From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
John Stultz <john.stultz@linaro.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: Wed, 15 Apr 2020 18:53:06 -0400 [thread overview]
Message-ID: <20200415185306.417c18c3@gandalf.local.home> (raw)
In-Reply-To: <20200415224214.GP2483@worktop.programming.kicks-ass.net>
On Thu, 16 Apr 2020 00:42:14 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Apr 15, 2020 at 03:04:59PM -0700, Paul E. McKenney wrote:
> >
> > My guess is that invoking rcu_irq_enter() and rcu_irq_exit() around every
> > potential call into module code out of the PM code is a non-starter,
> > but I cannot prove that either way.
>
> Isn't that exactly what cpu_pm_notify() is doing?
That was originally my concern, but I didn't look at cpu_pm_notify(), until
I was about to add that to it ;-) Then noticed, it was already there
(making my last email rather confusing as I wrote half of it before seeing
this, and then continued that email after the fact).
-- Steve
next prev parent reply other threads:[~2020-04-15 22:53 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 [this message]
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
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=20200415185306.417c18c3@gandalf.local.home \
--to=rostedt@goodmis.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=peterz@infradead.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 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).