Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757142Ab3HMLl1 (ORCPT ); Tue, 13 Aug 2013 07:41:27 -0400 Received: from e28smtp03.in.ibm.com ([122.248.162.3]:33343 "EHLO e28smtp03.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756600Ab3HMLl0 (ORCPT ); Tue, 13 Aug 2013 07:41:26 -0400 Message-ID: <520A1B5E.8040105@linux.vnet.ibm.com> Date: Tue, 13 Aug 2013 17:11:18 +0530 From: "Naveen N. Rao" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130806 Thunderbird/17.0.8 MIME-Version: 1.0 To: Mauro Carvalho Chehab CC: Borislav Petkov , tony.luck@intel.com, bhelgaas@google.com, rostedt@goodmis.org, rjw@sisk.pl, lance.ortiz@hp.com, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Aristeu Rozanski Filho Subject: Re: [PATCH 3/3] mce: acpi/apei: trace: Enable ghes memory error trace event References: <1375986471-27113-1-git-send-email-naveen.n.rao@linux.vnet.ibm.com> <1375986471-27113-4-git-send-email-naveen.n.rao@linux.vnet.ibm.com> <20130808163822.67e0828a@samsung.com> <20130810180322.GC4155@pd.tnic> <20130812083355.47c1bae8@samsung.com> <5208D80D.5030206@linux.vnet.ibm.com> <20130812114404.3bd64fa0@samsung.com> In-Reply-To: <20130812114404.3bd64fa0@samsung.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-MML: No X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13081311-3864-0000-0000-0000099219C2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1025 Lines: 24 On 08/12/2013 08:14 PM, Mauro Carvalho Chehab wrote: >> But, this only seems to expose the APEI data as a string >> and doesn't look to really make all the fields available to user-space >> in a raw manner. Not sure how well this can be utilised by a user-space >> tool. Do you have suggestions on how we can do this? > > There's already an userspace tool that handes it: > https://git.fedorahosted.org/cgit/rasdaemon.git/ > > What is missing there on the current version is the bits that would allow > to translate from APEI way to report an error (memory node, card, module, > bank, device) into a DIMM label[1]. If I'm reading this right, all APEI data seems to be squashed into a string in mc_event. Also, the fru id/text don't seem to be passed to user-space. - Naveen -- 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/