From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] 3/3: MCA/MCE correctable error handling Date: Wed, 22 Aug 2007 17:10:24 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christoph Egger , xen-devel@lists.xensource.com Cc: Gavin.Maltby@sun.com, Jan Beulich List-Id: xen-devel@lists.xenproject.org On 22/8/07 17:05, "Keir Fraser" wrote: >> The polling routine that is in the -unstable tree (the version taken from >> Linux) runs every 15 seconds without adjustments. >> 1Hz causes too much system load for a healthy system IMO. >> That's why I introduced the adjustments with use of hw threshold registers >> to come to a compromise solution. > > What's the deal here? Do correctable errors not cause an MCE, yet are still > detected via the machine-check architecture (albeit by a polling method)? > > Are there going to be patches on the Linux side to pick up this MCA info? > What is Linux going to do with it, apart from log it (which Xen can already > do itself)? Or is this all Solaris-specific? Oh, and is AMD-specific code really needed in non-fatal.c? I though the MCA stuff was architectural now rather than vendor specific? If there are vendor-specific extensions then they belong in the vendor's .c file. -- Keir