Re: [PATCH net-next v5 1/4] printk: Add execution context (task name/CPU) to printk_info
From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-01-31 01:32:46
Also in:
lkml
From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-01-31 01:32:46
Also in:
lkml
On Wed, 28 Jan 2026 06:17:37 -0800 Breno Leitao wrote:
+config CONSOLE_HAS_EXECUTION_CTX + bool + help + Selected by console drivers that support execution context + (task name/CPU) in their output. This enables PRINTK_EXECUTION_CTX + to provide the necessary infrastructure. + +config PRINTK_EXECUTION_CTX + bool "Include execution context (task/CPU) in printk messages" + depends on PRINTK && CONSOLE_HAS_EXECUTION_CTX + default CONSOLE_HAS_EXECUTION_CTX
AFAIU the double-symbol thing serves no practical purpose? If none of the console drivers uses the metadata what would be the point of capturing it? Conversely if some console driver wants this data there's no option for the user to disable it. AFAICT this patch should only add one invisible symbol for capturing the context and have netcons enable it. I don't see a reason at this stage to prompt users with netcons disabled whether they want PRINTK_EXECUTION_CTX -- pw-bot: cr