From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: c/s 19576 vs. AMD systems
Date: Wed, 29 Apr 2009 11:49:54 +0100
Message-ID: <C61DEF62.9B70%keir.fraser@eu.citrix.com>
References: <49F847A2.76EA.0078.0@novell.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: <49F847A2.76EA.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/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/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: Jan Beulich <jbeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 29/04/2009 11:27, "Jan Beulich" <jbeulich@novell.com> wrote:

>> What do you suggest? Make the clip Intel-specific? We've only seen problems
>> with (a very few) Intel boxes, so handling AMD at all may be quite
>> unnecessary.
> 
> No - if BIOSes are broken, they can as well be an AMD systems. I'd rather
> take TOM2 and the mentioned SYS_CFG bit into account in that code (not
> the least because modern Linux also does so in its MTRR handling code).

I will consider fixes for theoretical BIOS problems in 3.5. I'm only putting
the test at all in 3.3/3.4 because we have actually seen problems on Intel
systems, and I will restrict the test to that scope.

 -- Keir