public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: no more MTRRs available ?
Date: Wed, 29 Jan 2003 16:14:46 +0000	[thread overview]
Message-ID: <20030129161446.GB32294@codemonkey.org.uk> (raw)
In-Reply-To: <20030129164552.182e0cb8.skraw@ithnet.com>

On Wed, Jan 29, 2003 at 04:45:52PM +0100, Stephan von Krawczynski wrote:
 
 > # cat /proc/mtrr
 > reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
 > reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
 > reg02: base=0xc0000000 (3072MB), size= 512MB: write-back, count=1
 > reg03: base=0xe0000000 (3584MB), size= 256MB: write-back, count=1
 > reg04: base=0xf0000000 (3840MB), size= 128MB: write-back, count=1
 > reg05: base=0xf7000000 (3952MB), size=  16MB: uncachable, count=1

Due to this 16MB hole, your BIOS has to set up a write-back range
covering 2048-16 (2032MB). Due to limitations on the way MTRRs work,
you can't do this all in 1, so you have to split it up over several.
The result is that you use up 5 MTRRs covering 1 range + 1 for the
unmapped 16MB. Leaving just two for..
 
 > reg06: base=0x100000000 (4096MB), size=4096MB: write-back, count=1
 > reg07: base=0x200000000 (8192MB), size=8192MB: write-back, count=1

So you really are out of MTRRs (There are only 8 on this CPU).
Does your BIOS have any option to disable this hole in low memory ?
I've seen similar things on laptops that use shared memory between
CPU & Graphics card, but I was unaware of anything like this on
desktop/server motherboards.

If this has onboard VGA, and theres a way to disable it, perhaps that
will work. (Even if it means plugging in a PCI/AGP video card)

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  parent reply	other threads:[~2003-01-29 16:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 15:23 no more MTRRs available ? Stephan von Krawczynski
     [not found] ` <Pine.LNX.4.44.0301291025240.18828-100000@coffee.psychology.mcmaster.ca>
2003-01-29 15:45   ` Stephan von Krawczynski
     [not found]     ` <Pine.LNX.4.44.0301291046490.18828-100000@coffee.psychology.mcmaster.ca>
2003-01-29 16:05       ` Stephan von Krawczynski
2003-01-29 16:20         ` Dave Jones
2003-01-29 17:15           ` Stephan von Krawczynski
2003-01-29 16:14     ` Dave Jones [this message]
2003-01-29 16:52       ` Dave Jones
2003-01-29 17:20     ` William Lee Irwin III
2003-01-29 17:48       ` Dave Jones
2003-01-29 18:00         ` William Lee Irwin III
2003-01-29 18:12           ` Dave Jones

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=20030129161446.GB32294@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.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