From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: c/s 19576 vs. AMD systems
Date: Wed, 29 Apr 2009 11:27:14 +0100 [thread overview]
Message-ID: <49F847A2.76EA.0078.0@novell.com> (raw)
In-Reply-To: <C61DDFD4.9B5B%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 29.04.09 11:43 >>>
>On 29/04/2009 09:53, "Jan Beulich" <jbeulich@novell.com> 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.
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).
Jan
next prev parent reply other threads:[~2009-04-29 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 8:53 c/s 19576 vs. AMD systems Jan Beulich
2009-04-29 9:43 ` Keir Fraser
2009-04-29 10:27 ` Jan Beulich [this message]
2009-04-29 10:49 ` Keir Fraser
2009-04-29 17:23 ` Frank Arnold
2009-04-30 6:58 ` Jan Beulich
2009-04-30 6:59 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F847A2.76EA.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.