Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751854Ab0KYEfV (ORCPT ); Wed, 24 Nov 2010 23:35:21 -0500 Received: from mga14.intel.com ([143.182.124.37]:59268 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751593Ab0KYEfT (ORCPT ); Wed, 24 Nov 2010 23:35:19 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.59,252,1288594800"; d="scan'208";a="353034086" Subject: Re: [PATCH 0/2] Generic hardware error reporting support From: Huang Ying To: Mark Lord Cc: huang ying , Linus Torvalds , Len Brown , "linux-kernel@vger.kernel.org" , Andi Kleen , "linux-acpi@vger.kernel.org" , Peter Zijlstra , Andrew Morton , Ingo Molnar , Mauro Carvalho Chehab , Borislav Petkov , Thomas Gleixner In-Reply-To: <4CEDCCF5.5030308@teksavvy.com> References: <1290154233-28695-1-git-send-email-ying.huang@intel.com> <4CEB0037.3000303@teksavvy.com> <1290472198.2903.156.camel@yhuang-dev> <4CEDCCF5.5030308@teksavvy.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 25 Nov 2010 12:35:15 +0800 Message-ID: <1290659715.2903.299.camel@yhuang-dev> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1753 Lines: 43 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/