From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: question about MTRR areas on x86_64
Date: Thu, 14 Oct 2004 16:04:41 +0200 [thread overview]
Message-ID: <416E8779.3020303@shadowconnect.com> (raw)
In-Reply-To: <m1acupefrn.fsf@ebiederm.dsl.xmission.com>
Hello,
Eric W. Biederman wrote:
> Andi Kleen <ak@muc.de> writes:
>>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.
Sorry, for not answering, but somehow i never received your e-mail. :-(
> And the BIOS is using overlapping MTRRs because otherwise it would run
> out.
Okay...
>>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.
I've seen there is already a patch around to add initial PAT support. So
i think it's only a question of time until it is included :-D If there is
something i could help with please let me know.
Thanks to both of you for helping.
Best regards,
Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)
Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany
Phone: +49 82 82/99 51-0
Fax: +49 82 82/99 51-11
E-Mail: Markus.Lidel@shadowconnect.com
URL: http://www.shadowconnect.com
next prev parent reply other threads:[~2004-10-14 14:00 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 ` question about MTRR areas on x86_64 Andi Kleen
2004-10-14 10:49 ` Eric W. Biederman
2004-10-14 14:04 ` Markus Lidel [this message]
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=416E8779.3020303@shadowconnect.com \
--to=markus.lidel@shadowconnect.com \
--cc=ak@muc.de \
--cc=ebiederm@xmission.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