Thread (7 messages) 7 messages, 2 authors, 2012-12-10

Re: [PATCH RT 2/2][RFC] let RCU stall messages escape with CONFIG_PREEMPT_RT_FULL

From: Frank Rowand <hidden>
Date: 2012-12-10 19:09:04
Also in: linux-arm-kernel, lkml

On 12/10/12 06:29, Paul E. McKenney wrote:
On Tue, Dec 04, 2012 at 08:52:21PM -0800, Frank Rowand wrote:
quoted
The printk()s in RCU stall warnings do not get flushed to the console
on ARM.  Add the oops_in_progress flag back into the special trylock case in
console_trylock_for_printk(), and set the flag using "bust_spinlocks(1)".
This allows the printk() output to be flushed to the console.

Signed-off-by: Frank Rowand <redacted>
Is bust_spinlocks(1) appropriate for all architectures, or should this
be conditioned on architectures that need oops_in_progress to be set?

							Thanx, Paul
Good question.  I don't know if the architectures that do not set
oops_in_progress do not need it, or if they just overlooked it.
I'll have to look a little bit deeper.

-Frank
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help