From: Andi Kleen <ak@muc.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andi Kleen <ak@muc.de>,
kraxel@suse.de, jsimmons@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use MTRRs by default for vesafb on x86-64
Date: Mon, 19 May 2003 12:37:17 +0200 [thread overview]
Message-ID: <20030519103717.GC15709@averell> (raw)
In-Reply-To: <m1of2233ds.fsf@frodo.biederman.org>
On Sat, May 17, 2003 at 12:58:39AM +0200, Eric W. Biederman wrote:
> I don't know if this affects the frame buffers per se.
>
> But often BIOS's on systems with large amounts of memory configure
> overlapping mtrrs (where an uncacheable mtrr would override a larger
> cacheable range). To date this has confused the linux mtrr code when
> it tries to modify things, and you cannot properly setup mtrrs. I
> believe this applies to both the fb case as well as X.
Interesting. Perhaps it would be really better to use change_page_attr()
with PAT for this. It would avoid these problems.
-Andi
next prev parent reply other threads:[~2003-05-19 10:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 14:56 [PATCH] Use MTRRs by default for vesafb on x86-64 Andi Kleen
2003-05-15 15:16 ` Dave Jones
2003-05-15 15:20 ` Andi Kleen
2003-05-15 15:25 ` Dave Jones
2003-05-16 20:51 ` Alan Cox
2003-05-18 5:39 ` Andi Kleen
2003-05-18 16:11 ` Jamie Lokier
2003-05-18 20:40 ` Alan Cox
2003-05-18 22:34 ` Jamie Lokier
2003-05-18 22:52 ` Dave Jones
2003-05-18 23:33 ` Jamie Lokier
2003-05-19 0:02 ` Dave Jones
2003-05-19 0:28 ` Jamie Lokier
2003-05-19 1:24 ` Dave Jones
2003-05-16 22:58 ` Eric W. Biederman
2003-05-19 10:37 ` Andi Kleen [this message]
2003-05-19 12:26 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2003-05-19 9:16 Etienne Lorrain
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=20030519103717.GC15709@averell \
--to=ak@muc.de \
--cc=ebiederm@xmission.com \
--cc=jsimmons@infradead.org \
--cc=kraxel@suse.de \
--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