[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290472198.2903.156.camel@yhuang-dev>
Date: Tue, 23 Nov 2010 08:29:58 +0800
From: Huang Ying <ying.huang@...el.com>
To: Mark Lord <kernel@...savvy.com>
Cc: huang ying <huang.ying.caritas@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Len Brown <lenb@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andi Kleen <andi@...stfloor.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Mauro Carvalho Chehab <mchehab@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 0/2] Generic hardware error reporting support
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.
> Have this obscure new tool simply parse the log messages,
> and the send/save the data whatever way you like.
>
> No new specialized kernel API required.
Adding a new device file will be seen as a new kernel API?
Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists