diff options
| author | Leonardo Bras <[email protected]> | 2020-05-12 18:45:35 -0300 |
|---|---|---|
| committer | Michael Ellerman <[email protected]> | 2020-06-02 20:59:07 +1000 |
| commit | af2876b501e42c3fb5174cac9dd02598436f0fdf (patch) | |
| tree | 4ec069414fb9c0383185ebc4fb9cf59b81857878 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | b6eca183e23e7a6625a0d2cdb806b7cd1abcd2d2 (diff) | |
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 <[email protected]>
Signed-off-by: Leonardo Bras <[email protected]>
Signed-off-by: Michael Ellerman <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions