Re: [PATCH 7/8] ACPI, APEI, CPER: Cleanup CPER memory error outputformat

[Naveen N. Rao]

On 10/14/2013 10:42 PM, Tony Luck wrote:
> On Mon, Oct 14, 2013 at 3:36 AM, Borislav Petkov <bp@xxxxxxxxx> wrote:
> > On Mon, Oct 14, 2013 at 12:55:00AM -0400, Chen Gong wrote:
> > > Because most of data in CPER are empty or unimportant.
> >
> > It is not about whether it is important or not - the question is whether
> > changing existing functionality which someone might rely upon is a
> > problem here? Someone might be expecting exactly those messages to
> > appear in dmesg.

If so, how will disabling dmesg output and switching to a trace event 
help? The user-space program will still break unless they add support 
for that trace event, right?

I'm not sure if we actually provide guarantees w.r.t kernel log 
messages. The issue in this specific scenario is the sheer verbosity of 
the log messages. I personally feel that it will be good if we can 
simplify the log output.

Thanks,
Naveen

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/