diff options
author | Will Deacon <will.deacon@arm.com> | 2015-12-21 19:44:27 +0300 |
---|---|---|
committer | Will Deacon <will.deacon@arm.com> | 2015-12-21 20:26:02 +0300 |
commit | c9cd0ed925c0b927283d4739bfe689eb9d1e9dfd (patch) | |
tree | 4ff8861114aa41098864b5b56f6798de4a817831 /tools/perf/scripts/python/call-graph-from-sql.py | |
parent | 20380bb390a443b2c5c8800cec59743faf8151b4 (diff) | |
download | linux-c9cd0ed925c0b927283d4739bfe689eb9d1e9dfd.tar.xz |
arm64: traps: address fallout from printk -> pr_* conversion
Commit ac7b406c1a9d ("arm64: Use pr_* instead of printk") was a fairly
mindless s/printk/pr_*/ change driven by a complaint from checkpatch.
As is usual with such changes, this has led to some odd behaviour on
arm64:
* syslog now picks up the "pr_emerg" line from dump_backtrace, but not
the actual trace, which leads to a bunch of "kernel:Call trace:"
lines in the log
* __{pte,pmd,pgd}_error print at KERN_CRIT, as opposed to KERN_ERR
which is used by other architectures.
This patch restores the original printk behaviour for dump_backtrace
and downgrade the pgtable error macros to KERN_ERR.
Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions