From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Alan Hourihane <alanh@fairlite.demon.co.uk>
Cc: dri-devel@lists.sf.net,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: DRM & MTRR's
Date: Fri, 23 Sep 2005 22:07:58 +0800 [thread overview]
Message-ID: <43340C3E.5070005@gmail.com> (raw)
In-Reply-To: <1127475052.9377.18.camel@jetpack.demon.co.uk>
Alan Hourihane wrote:
> Has anyone any objections to me removing the MTRR code from the DRM.
>
> It doesn't have the intimate knowledge needed to properly configure
> MTRR's and fails in many cases.
>
> There are two cases currently, one for the framebuffer and a second for
> the entire AGP space.
>
> Certainly in Intel hardware this is the same memory space and you always
> get bogus error messages in your kernel logs as things fail due to lack
> of boundary checks.
>
> I'm more of the opinion that it should be left up to userspace to
> configure MTRR's if it indeed wants them and we shouldn't force them
> within the DRM.
>
> Additionally, the Xserver (for user-space) already sets up the MTRR's,
> as should Xgl (Xegl) or other user space apps.
>
> What makes the situation a little worse is that vesafb (and other *fb
> drivers) also setup an mtrr which frequently stops subsequent processes
> from adding a new one that overlaps an existing write-combining range.
> But the *fb drivers do provide a nomtrr option in many cases. (But I'd
> like to remove it from them too :-) or at least default those to off)
I don't know the repercussions of defaulting to nomtrr. But I would
surmise that a large percentage of users gives more importance to X/DRI
performance than console performance (majority of vesafb users still
use redraw for scrolling where ypan is magnitudes faster, so I'm pretty
sure defaulting vesafb to nomtrr will not be noticeable to most users,
they probably go straight to X anyway :-)
I cannot decide on this alone, so I'm going to CC the fbdev-devel list.
Perhaps I can submit a patch that defaults all drivers to nomtrr and a
big warning about mtrr not being set in dmesg. If I don't get any
backlash for a few patch cycles, I can make this permanent.
Tony
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next parent reply other threads:[~2005-09-23 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1127475052.9377.18.camel@jetpack.demon.co.uk>
2005-09-23 14:07 ` Antonino A. Daplas [this message]
2005-10-10 19:58 ` DRM & MTRR's Alan Hourihane
2005-10-10 22:06 ` Antonino A. Daplas
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=43340C3E.5070005@gmail.com \
--to=adaplas@gmail.com \
--cc=alanh@fairlite.demon.co.uk \
--cc=dri-devel@lists.sf.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.