diff options
author | Leonardo Bras <leobras.c@gmail.com> | 2020-05-13 00:45:35 +0300 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2020-06-02 13:59:07 +0300 |
commit | af2876b501e42c3fb5174cac9dd02598436f0fdf (patch) | |
tree | 4ec069414fb9c0383185ebc4fb9cf59b81857878 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | b6eca183e23e7a6625a0d2cdb806b7cd1abcd2d2 (diff) | |
download | linux-af2876b501e42c3fb5174cac9dd02598436f0fdf.tar.xz |
powerpc/crash: Use NMI context for printk when starting to crash
Currently, if printk lock (logbuf_lock) is held by other thread during
crash, there is a chance of deadlocking the crash on next printk, and
blocking a possibly desired kdump.
At the start of default_machine_crash_shutdown, make printk enter
NMI context, as it will use per-cpu buffers to store the message,
and avoid locking logbuf_lock.
Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Leonardo Bras <leobras.c@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20200512214533.93878-1-leobras.c@gmail.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions