WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] x86: machine check exception handling

To: Christoph Egger <Christoph.Egger@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] x86: machine check exception handling
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Thu, 21 Jun 2007 15:59:47 +0100
Cc: Gavin Maltby <Gavin.Maltby@xxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>
Delivery-date: Thu, 21 Jun 2007 07:57:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200706211638.47367.Christoph.Egger@xxxxxxx>
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: Ace0FM8VDcOwtCAIEdyfwwAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] x86: machine check exception handling
User-agent: Microsoft-Entourage/11.3.3.061214
On 21/6/07 15:38, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:

> That's not possible. The #MC handler and the polling handler (in non-fatal.c)
> (are going to) do something completely different than any OS will ever do.
> See the discussion with the subject "MCA/MCE concept" for more information.

Well, then I guess these files will change wholesale when this new MCE
architecture is ready. That's fine.

> In opposition to the polling handler, #MC interruption is *very* bad.
> A #MC always means, that an uncorrectable ECC error is detected
> by the hw. First you have to figure out, who is impacted: Is it Xen, Dom0 or
> DomU?
> In case of Xen and Dom0 you can only do something using hw correction
> features or crash. In case of DomU, you can kill DomU in the worst case
> and keep the rest running.

If the error is such that it will impact correct execution of a Xen
interrupt handler (which generally do very little indeed) then you are
boned. Your #MC handler is unlikely to work properly either. Game over.

And you already know my opinion of the new "MCA/MCE concept".

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel