diff options
author | Steven Rostedt (Red Hat) <[email protected]> | 2014-06-19 17:33:32 -0400 |
---|---|---|
committer | Steven Rostedt <[email protected]> | 2014-11-19 22:01:21 -0500 |
commit | a9edc88093287183ac934be44f295f183b2c62dd (patch) | |
tree | 41e34afb4b458d73e0e374479c780d861cd10f7b /tools/perf/scripts/python/futex-contention.py | |
parent | afdc34a3d3b823a12a93b822ee1efb566f884032 (diff) |
x86/nmi: Perform a safe NMI stack trace on all CPUs
When trigger_all_cpu_backtrace() is called on x86, it will trigger an
NMI on each CPU and call show_regs(). But this can lead to a hard lock
up if the NMI comes in on another printk().
In order to avoid this, when the NMI triggers, it switches the printk
routine for that CPU to call a NMI safe printk function that records the
printk in a per_cpu seq_buf descriptor. After all NMIs have finished
recording its data, the seq_bufs are printed in a safe context.
Link: http://lkml.kernel.org/p/[email protected]
Link: http://lkml.kernel.org/r/[email protected]
Tested-by: Jiri Kosina <[email protected]>
Acked-by: Jiri Kosina <[email protected]>
Acked-by: Paul E. McKenney <[email protected]>
Reviewed-by: Petr Mladek <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/futex-contention.py')
0 files changed, 0 insertions, 0 deletions