From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] 3/3: MCA/MCE correctable error handling
Date: Thu, 23 Aug 2007 15:07:44 +0100
Message-ID: <C2F35340.14820%keir@xensource.com>
References: <200708230857.29134.Christoph.Egger@amd.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <200708230857.29134.Christoph.Egger@amd.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Cc: Gavin.Maltby@sun.com, Jan Beulich <jbeulich@novell.com>
List-Id: xen-devel@lists.xenproject.org

On 23/8/07 07:57, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

>> Oh, and is AMD-specific code really needed in non-fatal.c? I though the MCA
>> stuff was architectural now rather than vendor specific? If there are
>> vendor-specific extensions then they belong in the vendor's .c file.
> 
> AMD-specific is the use of the hw register code. Intel has some additional
> machine check MSR's containing the register set. Intel may add a structure
> to patch 2/3 that make use of them. Should I move the amd polling handler to
> amd.c ?

I think so.

 -- Keir