From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RT 2/2][RFC] let RCU stall messages escape with CONFIG_PREEMPT_RT_FULL
Date: Mon, 10 Dec 2012 06:29:14 -0800 [thread overview]
Message-ID: <20121210142914.GP2516@linux.vnet.ibm.com> (raw)
In-Reply-To: <50BED305.9090308@am.sony.com>
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 allows the printk() output to be flushed to the console.
>
> Signed-off-by: Frank Rowand <frank.rowand@am.sony.com>
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
> ---
> kernel/printk.c | 5 3 + 2 - 0 !
> kernel/rcutree.c | 14 14 + 0 - 0 !
> 2 files changed, 17 insertions(+), 2 deletions(-)
>
> Index: b/kernel/printk.c
> ===================================================================
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -1390,8 +1390,9 @@ static int console_trylock_for_printk(un
> {
> int retval = 0, wake = 0;
> #ifdef CONFIG_PREEMPT_RT_FULL
> - int lock = !early_boot_irqs_disabled && !irqs_disabled_flags(flags) &&
> - (preempt_count() <= 1);
> + int lock = oops_in_progress || (
> + !early_boot_irqs_disabled && !irqs_disabled_flags(flags) &&
> + (preempt_count() <= 1));
> #else
> int lock = 1;
> #endif
> Index: b/kernel/rcutree.c
> ===================================================================
> --- a/kernel/rcutree.c
> +++ b/kernel/rcutree.c
> @@ -758,6 +758,11 @@ static void print_other_cpu_stall(struct
> raw_spin_unlock_irqrestore(&rnp->lock, flags);
>
> /*
> + * Allow printk() to flush to device
> + */
> + bust_spinlocks(1);
> +
> + /*
> * OK, time to rat on our buddy...
> * See Documentation/RCU/stallwarn.txt for info on how to debug
> * RCU CPU stall warnings.
> @@ -799,6 +804,8 @@ static void print_other_cpu_stall(struct
>
> rcu_print_detail_task_stall(rsp);
>
> + bust_spinlocks(0);
> +
> force_quiescent_state(rsp, 0); /* Kick them all. */
> }
>
> @@ -808,6 +815,11 @@ static void print_cpu_stall(struct rcu_s
> struct rcu_node *rnp = rcu_get_root(rsp);
>
> /*
> + * Allow printk() to flush to device
> + */
> + bust_spinlocks(1);
> +
> + /*
> * OK, time to rat on ourselves...
> * See Documentation/RCU/stallwarn.txt for info on how to debug
> * RCU CPU stall warnings.
> @@ -820,6 +832,8 @@ static void print_cpu_stall(struct rcu_s
> if (!trigger_all_cpu_backtrace())
> dump_stack();
>
> + bust_spinlocks(0);
> +
> raw_spin_lock_irqsave(&rnp->lock, flags);
> if (ULONG_CMP_GE(jiffies, rsp->jiffies_stall))
> rsp->jiffies_stall = jiffies +
>
next prev parent reply other threads:[~2012-12-10 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 4:47 [PATCH RT 0/2][RFC] fix RCU stall warning on ARM Frank Rowand
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 [this message]
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=20121210142914.GP2516@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--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).