Re: [PATCH 0/2] Generic hardware error reporting support

Huang Ying
2010-11-25T04:35:19Z

On Thu, 2010-11-25 at 10:41 +0800, Mark Lord wrote:
> On 10-11-22 07:29 PM, Huang Ying wrote:
> > On Tue, 2010-11-23 at 07:43 +0800, Mark Lord wrote:
> >> On 10-11-20 08:06 PM, huang ying wrote:
> >>>
> >>> I have no objection to report hardware errors in system logs too. So
> >>> these people can get the information too. I just want to add another
> >>> tool oriented interface too. So that some other users (like cluster
> >>> administrator) can get their work done better too.
> >>
> >> So, use the standard interface for the tool: syslog.
> >
> > Although it may be possible to extract some information from syslog and
> > parse it in a fault tolerant way, we can only use that human oriented
> > interface for a tool? That sounds like hack.
>
> No, that sounds like the *NIX programming philosophy.
>
> You may have already noticed that most *NIX tools store
> and manage data in _text_ form. That makes it easy to
> understand, easy to parse/process, and generally better
> in almost every respect.

I have no objection to text form interface. I said printk is not a tool
oriented interface not because it is a text form interface but some
other issues. For example, messages from different CPU/context may be
interleaved; all kinds information mixed together, without overall
format or meta-data, etc.

> Other platforms (GNOME, MS-Windows) prefer a binary format
> that requires special tools to view/access. Ugh.

Linux kernel uses binary format interfaces too.

Best Regards,
Huang Ying