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


[Xen-devel] Re: c/s 19576 vs. AMD systems

To: Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: [Xen-devel] Re: c/s 19576 vs. AMD systems
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 29 Apr 2009 11:49:54 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 29 Apr 2009 03:50:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49F847A2.76EA.0078.0@xxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnItOBSmrOsbq3AQ7ifmcuXbtNvQAAA1pNT
Thread-topic: c/s 19576 vs. AMD systems
User-agent: Microsoft-Entourage/
On 29/04/2009 11:27, "Jan Beulich" <jbeulich@xxxxxxxxxx> 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

Xen-devel mailing list