From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank van der Linden Subject: Re: Re: [RFC] RAS(Part II)--MCA enalbing in XEN Date: Tue, 24 Feb 2009 12:07:16 -0700 Message-ID: <49A44564.3080505@Sun.COM> References: <200902181905.55015.Christoph.Egger@amd.com> <200902191725.32556.Christoph.Egger@amd.com> <499F1A1A.2080808@Sun.COM> <49A4423F.7070702@Sun.COM> <2E9E6F5F5978EF44A8590E339E888CF988279945@irsmsx503.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <2E9E6F5F5978EF44A8590E339E888CF988279945@irsmsx503.ger.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Kleen, Andi" Cc: Christoph Egger , "xen-devel@lists.xensource.com" , "Jiang, Yunhong" , "Ke, Liping" , Gavin Maltby , Keir Fraser List-Id: xen-devel@lists.xenproject.org Kleen, Andi wrote: >> MCA information is highly specific to the hardware. > > Actually Intel has architectural machine checks and except for > some optional addon information explicitely marked it's all architectural > (as in defined to stay the same going forward) True, I probably expressed myself poorly here. I meant to say: it's a physical hardware error, and in an unmodified virtualized environment the information about the physical hardware isn't there. > For DomU translation of the address is needed, that's correct. > For Dom0 logging physical is good because the logging tools > might need that. Right. As far as I understand it, this patch proposes to deliver the actual physical information to dom0 via the existing vIRQ mechanism, while the vMCE mechanism delivers virtualized info to any guest (both dom0 and domU). - Frank