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] [pvops-dom0] Adding MCA logging support in pv_ops

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] [pvops-dom0] Adding MCA logging support in pv_ops
From: "Ke, Liping" <liping.ke@xxxxxxxxx>
Date: Thu, 30 Jul 2009 16:45:58 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 30 Jul 2009 01:47:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A7174D3020000780000D350@xxxxxxxxxxxxxxxxxx>
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: <E2263E4A5B2284449EEBD0AAB751098402CDF6599F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A7174D3020000780000D350@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoQ7wbznIKMhsgbSkuRj2DGnvnE4AAAsHRg
Thread-topic: [Xen-devel] [pvops-dom0] Adding MCA logging support in pv_ops
Hi,  Jan& Jeremy

Thanks for the feedback. This is back port from 2.6.18 old DOM0 Kernel.

And also, I got some feedbacks from Andi Kleen. I will modify all of them and 
resend it tomorrow.

Thanks a lot!

Jan Beulich wrote:
>>>> "Ke, Liping" <liping.ke@xxxxxxxxx> 30.07.09 07:15 >>>
>> This patch is backport from DOM0 cs902
> What base kernel version is this against? I noticed that in .31
> struct mce doesn't have a res1 field anymore, and hence there's no
> place to (compatibly) store mc_bank->mc_ctrl2. Do you have any plans
> on how 
> to address this? Additionally, the new use of the space previously
> consumed by the res1 field seems to put under question whether that
> was actually forward compatible (namely, whether it might confuse
> newer user space tools).
> Thanks, Jan

Xen-devel mailing list