Re: [PATCH 26/26 v5] x86/nmi: Perform a safe NMI stack trace on all CPUs

On Fri 2014-11-14 23:59:13, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > 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

Re: [PATCH 26/26 v5] x86/nmi: Perform a safe NMI stack trace on all CPUs

On Fri 2014-11-14 23:59:13, Steven Rostedt wrote: From: Steven Rostedt (Red Hat) rost...@goodmis.org 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

[PATCH 26/26 v5] x86/nmi: Perform a safe NMI stack trace on all CPUs

From: "Steven Rostedt (Red Hat)" 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

[PATCH 26/26 v5] x86/nmi: Perform a safe NMI stack trace on all CPUs

From: Steven Rostedt (Red Hat) rost...@goodmis.org 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