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 4/4]Enable CMCI (Corrected Machine Check Error In

To: "Frank.Vanderlinden@xxxxxxx" <Frank.Vanderlinden@xxxxxxx>, Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: RE: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Wed, 14 Jan 2009 10:11:55 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Delivery-date: Tue, 13 Jan 2009 18:13:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <496CCF8A.3060906@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E2263E4A5B2284449EEBD0AAB751098401C4C32E95@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200901131221.23669.Christoph.Egger@xxxxxxx> <496CC5F0.6020007@xxxxxxx> <200901131811.23330.Christoph.Egger@xxxxxxx> <496CCF8A.3060906@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acl1pJrlhSouk4SYRtGD7HUYRYPQqAAQ9j2A
Thread-topic: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
Frank.Vanderlinden@xxxxxxx <mailto:Frank.Vanderlinden@xxxxxxx> wrote:
> Christoph Egger wrote:
> 
>> The patches I have seen so far, don't touch the public API at all.
>> But Intel did. That's the point in this discussion.
> 
> Actually, it seems we did add a few things that changed it.
> But looking
> at our changes now, we might not need them (like mc_apicid; it appears
> we don't actually use it anywhere).

For the mc_apicid, I think it gives informatoin for the whole topology 
information of the system, and will be helpful if needed in future. That's the 
reason we adopt the changes in our patch. Of course, we can get them through 
translate the mc_coreid to the apic_id, requiring dom0 cache the translation or 
have a hypercall for it. 

> 
> But, I'll have to get back to you on that after I've brought
> the changes
> up to xen-unstable level.

Yes, I suggest we hold the discussion till your changes are submited to 
upstream. 

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