aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/proc.py
diff options
context:
space:
mode:
authorPaul E. McKenney <[email protected]>2016-11-29 05:49:06 -0800
committerPaul E. McKenney <[email protected]>2017-01-23 11:37:12 -0800
commit7aa92230c9e86b2150f718185f70e0af592e290b (patch)
treea0402e24bc7048f590a7bffce9953845dfdc5fb9 /scripts/gdb/linux/proc.py
parentb201fa67371862229f27a1f022196423aa5c7381 (diff)
rcu: Once again use NMI-based stack traces in stall warnings
This commit is for all intents and purposes a revert of bc1dce514e9b ("rcu: Don't use NMIs to dump other CPUs' stacks"). The reason to suppose that this can now safely be reverted is the presence of 42a0bb3f7138 ("printk/nmi: generic solution for safe printk in NMI"), which is said to have made NMI-based stack dumps safe. However, this reversion keeps one nice property of bc1dce514e9b ("rcu: Don't use NMIs to dump other CPUs' stacks"), namely that only those CPUs blocking the grace period are dumped. The new trigger_single_cpu_backtrace() is used to make this happen, as suggested by Josh Poimboeuf. Reported-by: Vince Weaver <[email protected]> Signed-off-by: Paul E. McKenney <[email protected]> Cc: Petr Mladek <[email protected]> Cc: Peter Zijlstra <[email protected]> Reviewed-by: Josh Poimboeuf <[email protected]> Reviewed-by: Petr Mladek <[email protected]> Reviewed-by: Josh Triplett <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/proc.py')
0 files changed, 0 insertions, 0 deletions