From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: smp: Silence suspicious RCU usage with ipi tracepoints
Date: Mon, 29 Jun 2015 11:02:51 +0100 [thread overview]
Message-ID: <20150629100251.GZ7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1435176858-9568-1-git-send-email-sboyd@codeaurora.org>
On Wed, Jun 24, 2015 at 01:14:18PM -0700, Stephen Boyd wrote:
> John Stultz reported an RCU splat on ARM with ipi trace events
> enabled. It looks like the same problem exists on ARM64.
>
> At this point in the IPI handling path we haven't called
> irq_enter() yet, so RCU doesn't know that we're about to exit
> idle and properly warns that we're using RCU from an idle CPU.
> Use trace_ipi_entry_rcuidle() instead of trace_ipi_entry() so
> that RCU is informed about our exit from idle.
>
> Cc: John Stultz <john.stultz@linaro.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
> Fixes: 45ed695ac10a "ARM64: add IPI tracepoints"
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
I can find no trace of your equivalent ARM patch in my mailbox, but my
comment is as relevant to that message as it is to this one.
The Fixes: line has a standard format, which is not the formatting above.
Please see Documentation/SubmittingPatches section 2. Thanks.
I've fixed it when applying the ARM version of this patch. However, I'm
left wondering whether the lack of update to change the "Silence" to "Fix"
which I _stumbled_ over later in this thread is laziness on your part -
had it not been for the malformed Fixes: line, I would not have known to
update that.
We all gets lots of email every day, expecting people to remember some
comment in the dim and distant past made to a similar but different patch
is not really on. Please ensure that you update your patches in future.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-06-29 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 20:14 [PATCH] ARM64: smp: Silence suspicious RCU usage with ipi tracepoints Stephen Boyd
2015-06-24 20:20 ` Paul E. McKenney
2015-06-24 21:29 ` Peter Zijlstra
2015-06-24 21:59 ` Stephen Boyd
2015-06-25 13:24 ` Catalin Marinas
2015-06-25 1:01 ` Steven Rostedt
2015-06-29 10:02 ` Russell King - ARM Linux [this message]
2015-06-29 11:23 ` Catalin Marinas
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=20150629100251.GZ7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).