[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXxy7usBz1-TTkVB@gmail.com>
Date: Fri, 30 Jan 2026 01:01:11 -0800
From: Breno Leitao <leitao@...ian.org>
To: John Ogness <john.ogness@...utronix.de>, pmladek@...e.com
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, pmladek@...e.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>, Andrew Morton <akpm@...ux-foundation.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org, asantostc@...il.com, efault@....de,
gustavold@...il.com, calvin@...nvd.org, jv@...sburgh.net, mpdesouza@...e.com,
kernel-team@...a.com
Subject: Re: [PATCH net-next v5 1/4] printk: Add execution context (task
name/CPU) to printk_info
On Wed, Jan 28, 2026 at 03:48:16PM +0106, John Ogness wrote:
> On 2026-01-28, Breno Leitao <leitao@...ian.org> wrote:
> > Extend struct printk_info to include the task name, pid, and CPU
> > number where printk messages originate. This information is captured
> > at vprintk_store() time and propagated through printk_message to
> > nbcon_write_context, making it available to nbcon console drivers.
> >
> > This is useful for consoles like netconsole that want to include
> > execution context in their output, allowing correlation of messages
> > with specific tasks and CPUs regardless of where the console driver
> > actually runs.
> >
> > The feature is controlled by CONFIG_PRINTK_EXECUTION_CTX, which is
> > automatically selected by CONFIG_NETCONSOLE_DYNAMIC. When disabled,
> > the helper functions compile to no-ops with no overhead.
> >
> > Suggested-by: John Ogness <john.ogness@...utronix.de>
> > Signed-off-by: Breno Leitao <leitao@...ian.org>
> > Signed-off-by: Petr Mladek <pmladek@...e.com>
>
> Reviewed-by: John Ogness <john.ogness@...utronix.de>
Thank you for the review. To confirm, it is acceptable to queue this for
the next netdev version, isn't it?
Powered by blists - more mailing lists