From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-clk@vger.kernel.org, linux@roeck-us.net, tony@atomide.com,
linux@arm.linux.org.uk, rostedt@goodmis.org, rjw@rjwysocki.net,
pavel@ucw.cz, mturquette@baylibre.com, sboyd@codeaurora.org
Subject: [GIT PULL arm] Use _rcuidle tracepoints to allow tracing from idle
Date: Thu, 26 May 2016 09:26:06 -0700 [thread overview]
Message-ID: <20160526162606.GA20023@linux.vnet.ibm.com> (raw)
Hello, Ingo,
This series changes a number of event tracepoints to their _rcuidle() form
to allow use from idle without lockdep-RCU complaints, a straightforward
modification that has been successfully applied many times. These splats
were found in testing by Guenter Roeck and Tony Lindgren, who have
both successfully tested the full series. Tony asked that I carry these
in -rcu:
http://lkml.kernel.org/g/20160426213630.GV5995@atomide.com
These have been posted to LKML, CCing relevant maintainers, who have
not objected to the proposed changes:
http://lkml.kernel.org/g/20160516184844.GA20144@linux.vnet.ibm.com
These maintainers are also CCed on this pull request.
They have also been subjected to 0day Test Robot and -next testing.
Thanx, Paul
next reply other threads:[~2016-05-26 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 16:26 Paul E. McKenney [this message]
2016-05-26 16:27 ` [GIT PULL arm] Use _rcuidle tracepoints to allow tracing from idle Paul E. McKenney
2016-06-08 13:33 ` Ingo Molnar
2016-06-08 15:16 ` 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=20160526162606.GA20023@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@roeck-us.net \
--cc=mingo@kernel.org \
--cc=mturquette@baylibre.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=sboyd@codeaurora.org \
--cc=tony@atomide.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).