From: Andi Kleen <ak@muc.de>
To: Dave Jones <davej@codemonkey.org.uk>, 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: Thu, 15 May 2003 17:20:11 +0200 [thread overview]
Message-ID: <20030515152011.GA19271@averell> (raw)
In-Reply-To: <20030515151633.GA6128@suse.de>
On Thu, May 15, 2003 at 05:16:33PM +0200, Dave Jones wrote:
> On Thu, May 15, 2003 at 04:56:40PM +0200, Andi Kleen wrote:
>
> > x86-64 cannot call the 32bit VESA BIOS. This means when vesafb is active
> > it does software copying in the vesa frame buffer. This is insanely slow
> > when the frame buffer is not marked for write combining.
> >
> > Some discussion showed that the use_mtrr flag was only off for some
> > old broken ET4000 ISA card. x86-64 has no ISA, so this is no concern.
> > Make the default depend on CONFIG_ISA.
>
> There are PCI ET4000's too. Though if we can get the PCI IDs for those,
> we can work around them with a quirk. I have one *somewhere*, but it'll
> take me a while to dig it out.
To make all 0.001 users left of them happy yes. I think the patch should
be applied anyways.
-Andi
next prev parent reply other threads:[~2003-05-15 15:09 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 [this message]
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
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=20030515152011.GA19271@averell \
--to=ak@muc.de \
--cc=davej@codemonkey.org.uk \
--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