From: Paolo Abeni <pabeni@redhat.com>
To: Breno Leitao <leitao@debian.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
pmladek@suse.com, john.ogness@linutronix.de
Cc: 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 v4 1/5] printk: Add execution context (task name/CPU) to printk_info
Date: Tue, 27 Jan 2026 15:58:17 +0100 [thread overview]
Message-ID: <a2540606-0cb5-474b-8a2c-57920bc3392b@redhat.com> (raw)
In-Reply-To: <20260123-nbcon-v4-1-46a5cf567926@debian.org>
On 1/23/26 1:17 PM, 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>
The netconsole bits in later patches LGTM, but we need explicit ack from
printk maintainers here.
Thanks,
Paolo
next prev parent reply other threads:[~2026-01-27 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 12:17 [PATCH net-next v4 0/5] net: netconsole: convert to NBCON console infrastructure Breno Leitao
2026-01-23 12:17 ` [PATCH net-next v4 1/5] printk: Add execution context (task name/CPU) to printk_info Breno Leitao
2026-01-27 14:58 ` Paolo Abeni [this message]
2026-01-27 20:43 ` John Ogness
2026-01-28 10:52 ` Breno Leitao
2026-01-23 12:17 ` [PATCH net-next v4 2/5] netconsole: extract message fragmentation into send_msg_udp() Breno Leitao
2026-01-23 12:17 ` [PATCH net-next v4 3/5] netconsole: convert to NBCON console infrastructure Breno Leitao
2026-01-23 12:17 ` [PATCH net-next v4 4/5] netconsole: Use printk context for CPU and task information Breno Leitao
2026-01-23 12:17 ` [PATCH net-next v4 5/5] netconsole: pass wctxt to send_msg_udp() for consistency 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=a2540606-0cb5-474b-8a2c-57920bc3392b@redhat.com \
--to=pabeni@redhat.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=pmladek@suse.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