Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751928Ab0KYE1U (ORCPT ); Wed, 24 Nov 2010 23:27:20 -0500 Received: from vms173001pub.verizon.net ([206.46.173.1]:45965 "EHLO vms173001pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751349Ab0KYE1S (ORCPT ); Wed, 24 Nov 2010 23:27:18 -0500 Date: Wed, 24 Nov 2010 23:27:01 -0500 (EST) From: Len Brown X-X-Sender: lenb@x980 To: Mark Lord Cc: Huang Ying , huang ying , Linus Torvalds , "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 Subject: Re: [PATCH 0/2] Generic hardware error reporting support In-reply-to: <4CEDCCF5.5030308@teksavvy.com> Message-id: 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> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 745 Lines: 18 > ... most *NIX tools store and manage data in _text_ form. If the hardware error dump is complicated there is a trade-off between making things human readable and putting a lot of comlicated parsing code into the kernel. Maybe the kernel should just dump hex "text" in some cases and let a user-program parse the syslog? What do do if the hardware error log is very large? Is there a limit on how much is practical to send through syslog? thanks, -Len Brown, Intel Open Source Technology Center -- 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/