From: Andi Kleen <ak@muc.de>
To: Markus Lidel <Markus.Lidel@shadowconnect.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about MTRR areas on x86_64
Date: Wed, 06 Oct 2004 00:15:35 +0200 [thread overview]
Message-ID: <m3vfdox14o.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2M5w2-y8-3@gated-at.bofh.it> (Markus Lidel's message of "Wed, 06 Oct 2004 00:00:22 +0200")
Markus Lidel <Markus.Lidel@shadowconnect.com> writes:
>
> Could it be because the machine has too much memory, or is there a bug in the I2O driver?
The problem comes from the BIOS who set up reg00 to be overlapping
over other areas. The Linux MTRR driver cannot deal with overlapping
MTRRs, in fact it is sometimes impossible because it could run
out of registers or violate some of the MTRR restrictions.
It's a long standing problem, eventual fix will be to get rid
of MTRRs completely and only use PAT. But it needs a bit more work.
-Andi
next parent reply other threads:[~2004-10-05 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2M5w2-y8-3@gated-at.bofh.it>
2004-10-05 22:15 ` Andi Kleen [this message]
2004-10-14 10:49 ` question about MTRR areas on x86_64 Eric W. Biederman
2004-10-14 14:04 ` Markus Lidel
2004-10-05 21:54 Markus Lidel
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=m3vfdox14o.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=Markus.Lidel@shadowconnect.com \
--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