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: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] x86: machine check exception handling
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 22 Jun 2007 08:15:25 +0100
Delivery-date: Fri, 22 Jun 2007 00:10:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <467B8EF2.76E4.0078.0@xxxxxxxxxx>
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: Ace0nRpzWRcgsCCQEdys7AAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] x86: machine check exception handling
User-agent: Microsoft-Entourage/11.3.3.061214
On 22/6/07 07:57, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>> 3. Most contentious, I'm sure: removed VMX changes that would keep
>> interrupts disabled across NMI/MCE. The reason is simply that SVM does not
>> bother with this. If there is a requirement that NMI/MCE be called with
>> particular constraints on EFLAGS, then we should make that clear and fix up
>> both VMX and SVM in a separate patch. The pain of this is that it would
>> probably require extra checks on critical vmexit paths. Is it *really* that
>> bad for #MC to get interrupted?
> 
> Yes, I think it is bad - the machine is known to be a in bad condition
> already,
> and by allowing external interrupts you make the situation even worse.
> Consequently I think SVM should be fixed to only conditionally enable
> interrupts, just like VMX does.

What issue do you think ExtInts will introduce? A crash before we get a
fatal error dump onto the Xen console? This argument seems more than a
little dubious to me. But if we want to complicate the CLI/STI logic of VMX
and SVM then I think we should do that by pushing STI/CLI (or STGI/CLGI)
handling into the individual cases of the main demux switch statements in
vmx.c and svm.c.

 -- Keir



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