Messages in this thread | | | Date | Sat, 7 Apr 2012 02:26:26 +0200 (CEST) | From | Jiri Kosina <> | Subject | Re: [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 > DEVICE= > 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 SUSE Labs
| |