WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[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 10:43:32 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 29 Apr 2009 02:44:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49F8318D.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: AcnIp6yF/MPJot3eTyufKrQRvK2nZgAB0ikq
Thread-topic: c/s 19576 vs. AMD systems
User-agent: Microsoft-Entourage/12.17.0.090302
On 29/04/2009 09:53, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> I'm afraid this change is going to hurt on AMD systems where memory extends
> beyond the 4Gb boundary: Both such systems that I have direct access to
> have their Intel MTRRs only defined up to the 4Gb boundary, yet through
> the use of AMD specific MSRs (SYS_CFG.Tom2ForceMemTypeWB and TOM2)
> the default memory type for everything beyond the 4Gb boundary is WB.
> On these systems there shouldn't be any clipping. I certainly can put together
> a patch for this, but it'll take me a couple of days until I'd get to it.

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.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel