public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: no more MTRRs available ?
Date: Wed, 29 Jan 2003 17:05:54 +0100	[thread overview]
Message-ID: <20030129170554.08dc6393.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301291046490.18828-100000@coffee.psychology.mcmaster.ca>

On Wed, 29 Jan 2003 10:51:03 -0500 (EST)
Mark Hahn <hahn@physics.mcmaster.ca> wrote:

> > > > what exactly does
> > > > 
> > > > 	mtrr: no more MTRRs available
> > > > 	mtrr: no more MTRRs available
> > > > 
> > > > during boot mean? What can I do against this? This comes up while
> > > > booting a system with 6GB and P-III 1.4 GHz (Serverworks chipset).
> > > > Kernel is 2.4.20.
> > > 
> > > you need to look at /proc/mtrr.
> > 
> > Thanks for your hint, but what does this tell me?
> 
> that your bios is stupid, I think.  mtrr's handle areas that are 
> powers of two in size (and >= 1M, I think).  the problem here is that
> the bios is trying to represent 4G of write-back ram and a 16M of 
> uncachable IO area (AGP aperture, I'm guessing).  the correct way
> to do this is a single 4G mtrr with an overlapping 16M one.

Ah, I see. So getting the above two messages would simply mean that there is no
table space left to add yet another two entries kernel gets from bios?

> do you have >4G ram?  that would explain the latter two.

Yes, this box has 6GB.

> note that you can fairly freely add/delete mtrr's from userspace.
> as long as you do it infrequently, I don't see why there would be 
> any risk or performance problem.

So the conclusion is that it does not look nice currently, but does not do any
harm (performance loss) either. I can live with that.
Thanks for your comments.

> > # 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
> > reg06: base=0x100000000 (4096MB), size=4096MB: write-back, count=1
> > reg07: base=0x200000000 (8192MB), size=8192MB: write-back, count=1
-- 
Regards,
Stephan

  parent reply	other threads:[~2003-01-29 15:56 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 [this message]
2003-01-29 16:20         ` Dave Jones
2003-01-29 17:15           ` Stephan von Krawczynski
2003-01-29 16:14     ` Dave Jones
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=20030129170554.08dc6393.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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