diff options
author | Dmitry Safonov <dima@arista.com> | 2020-06-08 21:30:35 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-06-09 09:39:11 -0700 |
commit | 0b2ad0c7ae0fb37dee4e8ae36b887c1d4db1f898 (patch) | |
tree | 5400ee766b2be468d6462739a5487bf610defe9f /arch/hexagon | |
parent | aeeb59d692c1bafecde3dfc47bfd0958fc96dfad (diff) | |
download | linux-0b2ad0c7ae0fb37dee4e8ae36b887c1d4db1f898.tar.gz linux-0b2ad0c7ae0fb37dee4e8ae36b887c1d4db1f898.tar.bz2 linux-0b2ad0c7ae0fb37dee4e8ae36b887c1d4db1f898.zip |
h8300: 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().
[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>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Link: http://lkml.kernel.org/r/20200418201944.482088-14-dima@arista.com
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/hexagon')
0 files changed, 0 insertions, 0 deletions