From: Robert Hancock <hancockrwd@gmail.com>
To: Volker Armin Hemmann <volkerarmin@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd64 + mtrr: only 3.1gb of 8gb are covered, kernel 2.6.30 and earlier.
Date: Fri, 21 Aug 2009 23:43:34 -0600 [thread overview]
Message-ID: <4A8F8586.5050300@gmail.com> (raw)
In-Reply-To: <200908211814.56800.volkerarmin@googlemail.com>
On 08/21/2009 10:14 AM, Volker Armin Hemmann wrote:
> Hi,
>
> I have an amd64 system with 8GB ram. Of these only 3.1GB are currently covered
> with mtrr:
> cat /proc/mtrr
> reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
> reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
> reg02: base=0x0c0000000 ( 3072MB), size= 128MB, count=1: write-back
>
> This is with a Phenom II X4. Mobo is an Asrock A770Crossfire with AMD 770
> chipset. Ram is 1066 ddr2 running at 800.
>
> Before that I had a X2 6000 where I had one more mtrr, covering additional
> 256mb with 6gb ram total.
>
> When I use the opensource driver, I get a 'mtrr disabled' message when X
> starts, nothing like that with fglrx. The results are the same.
>
> Is there anything that I can do about it? I already played with mtrr cleanup
> options - without any results.
I seem to recall hearing that on some newer AMD CPUs the memory above
4GB is either hardcoded to cacheable or set that way via some other
mechanism such that MTRRs aren't needed for it. Maybe someone else can
provide more details.
next prev parent reply other threads:[~2009-08-22 5:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 16:14 amd64 + mtrr: only 3.1gb of 8gb are covered, kernel 2.6.30 and earlier Volker Armin Hemmann
2009-08-22 5:43 ` Robert Hancock [this message]
2009-08-22 18:48 ` Yinghai Lu
2009-08-22 18:54 ` Volker Armin Hemmann
2009-08-22 19:04 ` Yinghai Lu
[not found] ` <200908222126.31390.volkerarmin@googlemail.com>
[not found] ` <86802c440908222322s44957498s72a76940f89271cf@mail.gmail.com>
2009-08-23 9:11 ` Volker Armin Hemmann
2009-08-27 1:13 ` Volker Armin Hemmann
2009-08-27 7:13 ` Yinghai Lu
2009-08-27 16:28 ` Volker Armin Hemmann
2009-09-19 20:11 ` Volker Armin Hemmann
2009-09-20 6:03 ` Yinghai Lu
2009-09-29 17:32 ` Volker Armin Hemmann
2009-09-29 19:23 ` Yinghai Lu
2009-09-29 19:24 ` Volker Armin Hemmann
-- strict thread matches above, loose matches on Subject: below --
2009-08-22 19:29 Volker Armin Hemmann
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=4A8F8586.5050300@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=volkerarmin@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox