From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: Enlin Mu <enlinmu@gmail.com>, Enlin Mu <enlin.mu@outlook.com>,
rostedt@goodmis.org, senozhatsky@chromium.org,
keescook@chromium.org, tony.luck@intel.com, gpiccoli@igalia.com,
enlin.mu@unisoc.com, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] printk: add cpu id information to printk() output
Date: Mon, 18 Sep 2023 11:00:48 +0206 [thread overview]
Message-ID: <87ttrrlv3b.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <ZQSHJ_786kZNjEDX@alley>
On 2023-09-15, Petr Mladek <pmladek@suse.com> wrote:
> The biggest problem is that it would change the format of the
> ringbuffer so that it would require updating external tools,
> working with crashdump, especially crash but there are also
> alternative python extensions for gdb.
I already have experience updating these external tools. It is
manageable. But I would prefer we had bigger changes to make. Let us not
forget your RFC [0] where you wanted to add similar metadata and
more. We should put all these changes into a single release.
John Ogness
[0] https://lore.kernel.org/lkml/20200923135617.27149-1-pmladek@suse.com
next prev parent reply other threads:[~2023-09-18 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 7:40 [PATCH] printk: add cpu id information to printk() output Enlin Mu
2023-09-15 8:34 ` John Ogness
2023-09-15 8:46 ` Enlin Mu
2023-09-15 9:53 ` Greg KH
2023-09-15 16:32 ` Petr Mladek
2023-09-18 8:54 ` John Ogness [this message]
2023-09-22 7:20 ` Enlin Mu
2023-09-22 8:03 ` Petr Mladek
2023-09-22 7:34 ` Enlin Mu
2023-09-22 7:47 ` Petr Mladek
2023-09-15 9:51 ` Greg KH
2023-09-15 16:31 ` Luck, Tony
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=87ttrrlv3b.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=enlin.mu@outlook.com \
--cc=enlin.mu@unisoc.com \
--cc=enlinmu@gmail.com \
--cc=gpiccoli@igalia.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tony.luck@intel.com \
/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