Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752769Ab0A0PGP (ORCPT ); Wed, 27 Jan 2010 10:06:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751772Ab0A0PGN (ORCPT ); Wed, 27 Jan 2010 10:06:13 -0500 Received: from mx1.redhat.com ([209.132.183.28]:16219 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751305Ab0A0PGM (ORCPT ); Wed, 27 Jan 2010 10:06:12 -0500 Message-ID: <4B605617.6050006@redhat.com> Date: Wed, 27 Jan 2010 13:04:55 -0200 From: Mauro Carvalho Chehab User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Andi Kleen CC: Ingo Molnar , Borislav Petkov , mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org, tglx@linutronix.de, Andreas Herrmann , Hidetoshi Seto , linux-tip-commits@vger.kernel.org, Peter Zijlstra , Fr??d??ric Weisbecker , Aristeu Rozanski , Doug Thompson , Huang Ying , Arjan van de Ven Subject: Re: [tip:x86/mce] x86, mce: Rename cpu_specific_poll to mce_cpu_specific_poll References: <20100121221711.GA8242@basil.fritz.box> <20100123051717.GA26471@elte.hu> <20100123075851.GA7098@liondog.tnic> <20100123090003.GA20056@elte.hu> <4B6032E7.1090900@redhat.com> <20100127143957.GE12522@basil.fritz.box> In-Reply-To: <20100127143957.GE12522@basil.fritz.box> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1240 Lines: 32 Andi Kleen wrote: > it only covers > parts of the space (some subset of Nehalems with a specific uncore). The changes for Xeon 55xx are minimal. I did some tests with the driver on it already. > This does not include Xeon 75xx where all this is quite different. I haven't the datasheets for 75xx, so I can't say for sure if it would be better to use the same driver or to fork it. >> I agree. The EDAC module handles memory errors for several memory controllers, >> including some on non-x86 architectures. Letting this decode to happen outside >> the kernel, just for a very few set of memory controllers, seems a bad idea. > > Again you can't do all the things mcelog does in kernel space only. Well, the error parsing can be done in kernel space in a standard way provided by the edac interface. I don't see why not the mcelog userspace shouldn't use the EDAC interface as one of its source, getting memory errors from it, avoiding the need of re-parsing the errors. Cheers, Mauro. -- 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/