summaryrefslogtreecommitdiff
path: root/virt
diff options
context:
space:
mode:
authorDmitry Safonov <dima@arista.com>2020-06-09 07:30:38 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2020-06-09 19:39:11 +0300
commitd1e9086dd99b2501a692e9dbccdb211ac6e09d14 (patch)
tree5ccfa2caef24ef2775c8e9bc47579f29bf6a5677 /virt
parent0b2ad0c7ae0fb37dee4e8ae36b887c1d4db1f898 (diff)
downloadlinux-d1e9086dd99b2501a692e9dbccdb211ac6e09d14.tar.xz
hexagon: add show_stack_loglvl()
Currently, the log-level of show_stack() depends on a platform realization. It creates situations where the headers are printed with lower log level or higher than the stacktrace (depending on a platform or user). Furthermore, it forces the logic decision from user to an architecture side. In result, some users as sysrq/kdb/etc are doing tricks with temporary rising console_loglevel while printing their messages. And in result it not only may print unwanted messages from other CPUs, but also omit printing at all in the unlucky case where the printk() was deferred. Introducing log-level parameter and KERN_UNSUPPRESSED [1] seems an easier approach than introducing more printk buffers. Also, it will consolidate printings with headers. Introduce show_stack_loglvl(), that eventually will substitute show_stack(). As a good side-effect die() now prints the stacktrace with KERN_EMERG aligned with other messages. [1]: https://lore.kernel.org/lkml/20190528002412.1625-1-dima@arista.com/T/#u Signed-off-by: Dmitry Safonov <dima@arista.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Acked-by: Brian Cain <bcain@codeaurora.org> Link: http://lkml.kernel.org/r/20200418201944.482088-15-dima@arista.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions