Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754935Ab3HOJim (ORCPT ); Thu, 15 Aug 2013 05:38:42 -0400 Received: from mail.skyhub.de ([78.46.96.112]:60560 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753089Ab3HOJij (ORCPT ); Thu, 15 Aug 2013 05:38:39 -0400 Date: Thu, 15 Aug 2013 11:38:31 +0200 From: Borislav Petkov To: Mauro Carvalho Chehab Cc: "Naveen N. Rao" , 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 Subject: Re: [PATCH 3/3] mce: acpi/apei: trace: Enable ghes memory error trace event Message-ID: <20130815093831.GA27616@pd.tnic> References: <20130810180322.GC4155@pd.tnic> <20130812083355.47c1bae8@samsung.com> <5208D80D.5030206@linux.vnet.ibm.com> <20130812125343.GE18018@pd.tnic> <520A16BD.30201@linux.vnet.ibm.com> <20130813124258.GC4077@pd.tnic> <520A6D98.9060204@linux.vnet.ibm.com> <20130813175809.GE4077@pd.tnic> <520B6282.6030906@linux.vnet.ibm.com> <20130814212211.544ee6a4@concha.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20130814212211.544ee6a4@concha.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1164 Lines: 32 On Wed, Aug 14, 2013 at 09:22:11PM -0300, Mauro Carvalho Chehab wrote: > 1) EDAC core needs to know that it should reject "hardware first" > drivers. -ENOPARSE. What do you mean? > 3) If BIOS vendors add later some solution to enumerate the DIMMS > per memory controller, channel, socket with APEI, the addition to the > existing driver would be trivial. Actually, with BIOS vendors wanting to do firmware-first strategy with DRAM errors, they must have a pretty good and intimate picture of the memory topology at hand. So it is only a logical consequence for them, when reporting a memory error to the OS to tell us the silkscreen label too, while at it. And if they do that, we don't need the additional layer - just a tracepoint from APEI and a userspace script. It's a whole another question if they don't do that. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- 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/