aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorGravatar Dmitry Safonov <dima@arista.com> 2020-06-08 21:32:07 -0700
committerGravatar Linus Torvalds <torvalds@linux-foundation.org> 2020-06-09 09:39:12 -0700
commit20da1e8bb06d0e3ccd172de3e193c987e88013cb (patch)
tree07e73fa586e3af27e478b1e5441e265a00aa8590 /include
parentxtensa: add loglvl to show_trace() (diff)
downloadlinux-20da1e8bb06d0e3ccd172de3e193c987e88013cb.tar.gz
linux-20da1e8bb06d0e3ccd172de3e193c987e88013cb.tar.bz2
linux-20da1e8bb06d0e3ccd172de3e193c987e88013cb.zip
xtensa: 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: Chris Zankel <chris@zankel.net> Cc: Max Filippov <jcmvbkbc@gmail.com> Link: http://lkml.kernel.org/r/20200418201944.482088-44-dima@arista.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions