Re: [PATCH 1/3] printk: use CONFIG_CONSOLE_LOGLEVEL_* directly
From: Sergey Senozhatsky <hidden>
Date: 2021-02-02 10:10:47
Also in:
dri-devel, linux-efi, lkml, platform-driver-x86
From: Sergey Senozhatsky <hidden>
Date: 2021-02-02 10:10:47
Also in:
dri-devel, linux-efi, lkml, platform-driver-x86
On (21/02/02 16:02), Masahiro Yamada wrote:
CONSOLE_LOGLEVEL_DEFAULT is nothing more than a shorthand of CONFIG_CONSOLE_LOGLEVEL_DEFAULT. When you change CONFIG_CONSOLE_LOGLEVEL_DEFAULT from Kconfig, almost all objects are rebuilt because CONFIG_CONSOLE_LOGLEVEL_DEFAULT is used in <linux/printk.h>, which is included from most of source files. In fact, there are only 4 users of CONSOLE_LOGLEVEL_DEFAULT: arch/x86/platform/uv/uv_nmi.c drivers/firmware/efi/libstub/efi-stub-helper.c drivers/tty/sysrq.c kernel/printk/printk.c So, when you change CONFIG_CONSOLE_LOGLEVEL_DEFAULT and rebuild the kernel, it is enough to recompile those 4 files.
Do you change CONFIG_CONSOLE_LOGLEVEL_DEFAULT so often that it becomes a problem? -ss