This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] 3/3: MCA/MCE correctable error handling

To: Christoph Egger <Christoph.Egger@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] 3/3: MCA/MCE correctable error handling
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 22 Aug 2007 17:10:24 +0100
Cc: Gavin.Maltby@xxxxxxx, Jan Beulich <jbeulich@xxxxxxxxxx>
Delivery-date: Wed, 22 Aug 2007 09:11:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2F21D68.1476D%keir@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acfk1ktAid8TLFDJEdyrvwAX8io7RQAAKbkO
Thread-topic: [Xen-devel] [PATCH] 3/3: MCA/MCE correctable error handling
User-agent: Microsoft-Entourage/
On 22/8/07 17:05, "Keir Fraser" <keir@xxxxxxxxxxxxx> 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

Xen-devel mailing list