From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: c/s 19576 vs. AMD systems Date: Wed, 29 Apr 2009 10:43:32 +0100 Message-ID: References: <49F8318D.76EA.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49F8318D.76EA.0078.0@novell.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: Jan Beulich Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 29/04/2009 09:53, "Jan Beulich" 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