[lkml]   [2012]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] printk: support structured and multi-facility log messages
On Wed, 4 Apr 2012, Kay Sievers wrote:

> - Output of dev_printk() is reliably machine-readable now. In addition
> to the printed plain text message, it creates a log dictionary with the
> following properties:
> SUBSYSTEM= - the driver-core subsytem name
> b12:8 - block dev_t
> c127:3 - char dev_t
> n8 - netdev ifindex
> +sound:card0 - subsystem:devname

One of the questions that hasn't been raised yet, and which I personally
consider crucial -- are we making printk() interface part of userspace ABI
now by this?

Today, we are free to change any printk()s and not feel guilty about it at
all. With this, we are making the whole thing much more systematic and
friendly for automatic userspace consumption. Nnot really different to,
for example uevents, which I believe everyone considers userspace ABI now.

Do we really want that?

Jiri Kosina

 \ /
  Last update: 2012-04-07 02:29    [W:0.123 / U:26.096 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site