aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/export-to-postgresql-report
diff options
context:
space:
mode:
authorGuilherme G. Piccoli <[email protected]>2023-02-26 13:08:38 -0300
committerAndrew Morton <[email protected]>2023-03-02 21:54:23 -0800
commitb905039e428d639adeebb719b76f98865ea38d4d (patch)
tree2c3318a1aa7bad662f702c8a2af43f35ea9da33b /tools/perf/scripts/python/bin/export-to-postgresql-report
parent359d62559f578dc1ac86fd2d198f1455e9d8ce04 (diff)
panic: fix the panic_print NMI backtrace setting
Commit 8d470a45d1a6 ("panic: add option to dump all CPUs backtraces in panic_print") introduced a setting for the "panic_print" kernel parameter to allow users to request a NMI backtrace on panic. Problem is that the panic_print handling happens after the secondary CPUs are already disabled, hence this option ended-up being kind of a no-op - kernel skips the NMI trace in idling CPUs, which is the case of offline CPUs. Fix it by checking the NMI backtrace bit in the panic_print prior to the CPU disabling function. Link: https://lkml.kernel.org/r/[email protected] Fixes: 8d470a45d1a6 ("panic: add option to dump all CPUs backtraces in panic_print") Signed-off-by: Guilherme G. Piccoli <[email protected]> Cc: <[email protected]> Cc: Baoquan He <[email protected]> Cc: Dave Young <[email protected]> Cc: Feng Tang <[email protected]> Cc: HATAYAMA Daisuke <[email protected]> Cc: Hidehiro Kawai <[email protected]> Cc: Kees Cook <[email protected]> Cc: Michael Kelley <[email protected]> Cc: Petr Mladek <[email protected]> Cc: Vivek Goyal <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions