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

xen-devel

[Top] [All Lists]

RE: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error In

To: Christoph Egger <Christoph.Egger@xxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Subject: RE: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: 2009年1月14日 10:58:54 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Keir, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: 2009年1月13日 18:59:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200901131221.23669.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/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> <200901121503.17232.Christoph.Egger@xxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401C4F02B3C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200901131221.23669.Christoph.Egger@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acl1cSkliOKgkcVfRwue2xdvc73ZywAfHWKQ
Thread-topic: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx <> wrote:
> On Tuesday 13 January 2009 03:12:51 Ke, Liping wrote:
>
> When I defined the API, I already knew that 5 is not enough for Intel.
> So I made struct mc_info large enough to keep multiple entities in any
> combination. I expected from you to fill struct mcinfo_extended two or
> three times into struct mc_info the same way as you do with
> struct mcinfo_bank. There's no (additional) allocation needed.
Just as Liping has pointed out, since there is size caculated in mcinfo_common, 
it should be ok for this changes, especially considering just increase the 
size, not decrease. 
Anyway, let's wait for Frank and Gavin's changes. 
BTW, do you know any usage for this MCA mechanism except Sun? We are 
considering more changes to Xen's MCA and some suggestion is send to mailing 
list (http://lists.xensource.com/archives/html/xen-devel/2008-12/msg00643.html 
gives three options ), we want get feedback from them and you, to avoid 
suprise in last minutes again.
Thanks
Yunhong Jiang
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: RE: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs , Jiang, Yunhong
Next by Date: Re: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs , Frank van der Linden
Previous by Thread: RE: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs , Ke, Liping
Next by Thread: Re: [Xen-devel] [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs , Frank van der Linden
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /