From: Frank Rowand <frank.rowand@am.sony.com>
To: <linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>,
<tglx@linutronix.de>, <paulmck@linux.vnet.ibm.com>,
<dipankar@in.ibm.com>, <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH RT 0/2][RFC] fix RCU stall warning on ARM
Date: Tue, 4 Dec 2012 20:47:22 -0800 [thread overview]
Message-ID: <50BED1DA.7070907@am.sony.com> (raw)
The RCU stall warning functions call trigger_all_cpu_backtrace()
to print a backtrace on each cpu. This function is only
implemented for x86. Add a version for ARM.
With CONFIG_PREEMPT_RT_FULL enabled, flushing the output from
printk() is inhibited in some contexts to avoid increasing
real time latencies. The RCU stall warnings are inhibited
on ARM due to this feature. (I have not tested whether this
is also the case on other architectures.) Add back the
oops_in_progress flag to allow the RCU stall warnings to
print immediately.
A third patch contains test scaffolding to force the stall
warnings to occur so that the other patches can be tested.
The third patch should __not__ added to the mainline
RT PREEMPT patch tree.
These patches apply to 3.6.7-rt18. They do not apply
cleanly to 3.0.xx.
next reply other threads:[~2012-12-05 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 4:47 Frank Rowand [this message]
2012-12-05 4:52 ` [PATCH RT 1/2][RFC] ARM version of arch_trigger_all_cpu_backtrace() Frank Rowand
2012-12-05 4:52 ` [PATCH RT 2/2][RFC] let RCU stall messages escape with CONFIG_PREEMPT_RT_FULL Frank Rowand
2012-12-10 14:29 ` Paul E. McKenney
2012-12-10 19:08 ` Frank Rowand
2012-12-05 4:52 ` [PATCH RT 0/2][RFC] fix RCU stall warning on ARM Frank Rowand
2012-12-05 5:05 ` Frank Rowand
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=50BED1DA.7070907@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=dipankar@in.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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