[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30f29fe6-8445-0016-8cdc-3ef99d43fbf5@redhat.com>
Date: Fri, 4 Oct 2019 09:48:24 -0500
From: Tony Asleson <tasleson@...hat.com>
To: John Ogness <john.ogness@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Petr Mladek <pmladek@...e.com>,
Andrea Parri <parri.andrea@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Theodore Ts'o <tytso@....edu>, Paul Turner <pjt@...gle.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Prarit Bhargava <prarit@...hat.com>,
Jeff Moyer <jmoyer@...hat.com>,
David Lehman <dlehman@...hat.com>
Subject: Re: Re: printk meeting at LPC
On 9/13/19 8:26 AM, John Ogness wrote:
> 9. Support for printk dictionaries will be discontinued. I will look
> into who is using this and why. If printk dictionaries are important for
> you, speak up now!
I think this functionality is important.
I've been experimenting with a change which adds dictionary data to
storage related printk messages so that a persistent durable id is
associated with them for filtering, eg.
$ journalctl -r _KERNEL_DURABLE_NAME=naa.0000000000bc614e
This has the advantage that when the device attachment changes across
reboots or detach/reattach cycles you can easily find its messages
throughout it's recorded history.
Other reasons were outlined when introduced, ref.
https://lwn.net/Articles/490690/
I believe this functionality hasn't been leveraged to its full potential
yet.
-Tony
Powered by blists - more mailing lists