From: Petr Mladek <pmladek@suse.com>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
john.ogness@linutronix.de,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
asantostc@gmail.com, efault@gmx.de, gustavold@gmail.com,
calvin@wbinvd.org, jv@jvosburgh.net, mpdesouza@suse.com,
kernel-team@meta.com
Subject: Re: [PATCH net-next v6 1/4] printk: Add execution context (task name/CPU) to printk_info
Date: Thu, 5 Feb 2026 09:09:49 +0100 [thread overview]
Message-ID: <aYRQTdNrzqRwClpQ@pathway.suse.cz> (raw)
In-Reply-To: <20260203-nbcon-v6-1-985f3bdb3267@debian.org>
On Tue 2026-02-03 09:23:52, Breno Leitao 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@linutronix.de>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
This version version works as advertized. Feel free to use:
Reviewed-by: Petr Mladek <pmladek@suse.com>
But feel free to remove CONSOLE_HAS_EXECUTION_CTX completely
as suggested by John. It is true that it is not that useful
at the moment. And I am not sure if it would ever have any
good use.
Best Regards,
Petr
next prev parent reply other threads:[~2026-02-05 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:23 [PATCH net-next v6 0/4] net: netconsole: convert to NBCON console infrastructure Breno Leitao
2026-02-03 17:23 ` [PATCH net-next v6 1/4] printk: Add execution context (task name/CPU) to printk_info Breno Leitao
2026-02-05 8:09 ` Petr Mladek [this message]
2026-02-03 17:23 ` [PATCH net-next v6 2/4] netconsole: extract message fragmentation into send_msg_udp() Breno Leitao
2026-02-03 17:23 ` [PATCH net-next v6 3/4] netconsole: convert to NBCON console infrastructure Breno Leitao
2026-02-03 17:23 ` [PATCH net-next v6 4/4] netconsole: Use printk context for CPU and task information Breno Leitao
2026-02-04 23:06 ` [PATCH net-next v6 0/4] net: netconsole: convert to NBCON console infrastructure John Ogness
2026-02-06 12:10 ` Breno Leitao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aYRQTdNrzqRwClpQ@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=calvin@wbinvd.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=gustavold@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=jv@jvosburgh.net \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdesouza@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox