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

2012-12-10 Thread Frank Rowand
On 12/10/12 06:29, Paul E. McKenney wrote: > On Tue, Dec 04, 2012 at 08:52:21PM -0800, Frank Rowand wrote: >> >> 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

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

2012-12-10 Thread Paul E. McKenney
On Tue, Dec 04, 2012 at 08:52:21PM -0800, Frank Rowand wrote: > > 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

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

2012-12-04 Thread Frank Rowand
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: