From: Rik Faith <faith@precisioninsight.com>
To: "Eric W. Biederman" <ebiederm+eric@ccr.net>
Cc: Rik Faith <faith@precisioninsight.com>,
James Simmons <jsimmons@edgeglobal.com>,
Linux MM <linux-mm@kvack.org>
Subject: Re: MMIO regions
Date: Sun, 10 Oct 1999 14:46:05 -0400 (EDT) [thread overview]
Message-ID: <14336.53971.896012.84699@light.alephnull.com> (raw)
In-Reply-To: [Eric W. Biederman <ebiederm+eric@ccr.net>] 10 Oct 1999 09:03:11 -0500
On 10 Oct 1999 09:03:11 -0500,
Eric W. Biederman <ebiederm+eric@ccr.net> wrote:
> Rik Faith <faith@precisioninsight.com> writes:
> > The cooperative locking system used by the DRI (see
> > http://precisioninsight.com/dr/locking.html) allows direct-rendering
> > clients to perform fine-grain locking only when the MMIO region is actually
> > being written. The overhead for this system is extremely low (about 2
> > instructions to lock, and 1 instruction to unlock). Cooperative locking
> > like this allows several threads that all map the same MMIO region to run
> > simultaneously on an SMP system.
>
> The difficulty is that all threads need to be run as root.
> Ouch!!!
No. The DRI assumes that direct-rendering clients are running as non-root
users. A direct-rendering client, with an open connection to the X server,
is allowed to mmap the MMIO region via a special device (additional
restrictions also apply). For more information, please see "A Security
Analysis of the Direct Rendering Infrastructure"
(http://precisioninsight.com/dr/security.html).
> Personally I see 3 functional ways of making this work on buggy single
> threaded hardware.
>
> 1) Allow only one process to have the MMIO/Frame buffer regions faulted in
> at a time. As simultaneous frame buffer and MMIO writes are reported to
> have hardware crashing side effects.
Faulting doesn't work on low-end (e.g., any PC-class hardware) because two
clients cannot intermingle their MMIO writes.
> 2) Convince user space to have dedicated drawing/rendering threads that
> are created with fork rather than clone. Then these threads can be
> cautiously scheduled to work around buggy hardware.
We don't want to require that large existing OpenGL applications be
re-written for Linux -- we'd like them to be easily ported to Linux. In
any case, I don't see how using processes instead of thread makes this
problem any easier.
> 3) Have a set of very low overhead syscalls that will manipulate MMIO,
> etc. This might work in conjunction with 2 and have a fast path that just
> makes nothing else is running that could touch the frame buffer.
> (With Linux cheap syscalls this may be possible)
One of the advantages of "direct rendering" is that the clients talk
directly to the hardware. Adding a syscall interface for MMIO will create
a significant performance hit (the whole reason for providing direct
rendering is performance -- if you add significant overhead in the
direct-rendering pathway, then you might as well just implement an
indirect-rendering solution).
> What someone (not me) needs to do is code up a multithreaded test
> application that shoots pictures to the screen, and needs these features.
> And run tests with multiple copies of said test application running. On
> various kernel configurations to see if it will work and give acceptable
> performance.
The DRI has been implemented and is available in XFree86 3.9.15 (and up).
The DRI supports multiple simultaneous direct-rendering clients.
> Extending the current architecture with just X server needing to be
> trusted doesn't much worry me. But we really need to find
> an alternative to encouraing SUID binary only games (and other
> intensive clients).
Just to clarify, the DRI does _not_ require that clients be SUID.
If you are interested in reading more about the DRI, there are several
high- and low-level design documents available from
http://precisioninsight.com/piinsights.html.
Those who are not familiar with the basic ideas and requirements for
direct-rendering should start with the following papers describing
implementations by SGI and HP:
[KBH95] Mark J. Kilgard, David Blythe, and Deanna Hohn. System Support for
OpenGL Direct Rendering. Proceedings of Graphics Interface '95, Quebec
City, Quebec, May 1995. Available from
http://reality.sgi.com/mjk/direct/direct.html
[K97] Mark J. Kilgard. Realizing OpenGL: Two Implementations of One
Architecture. SIGGRAPH/Eurographics Workshop on Graphics Hardware, Los
Angeles, August 3-4, 1997. Avaialble from
http://reality.sgi.com/opengl/twoimps/twoimps.html
[LCPGH98] Kevin T. Lefebvre, Robert J. Casey, Michael, J. Phelps, Courtney
D. Goeltzenleuchter, and Donley B. Hoffman. An Overview of the HP
OpenGL® Software Architecture. The Hewlett-Packard Journal, May 1998,
49(2): 9-18. Available from
http://www.hp.com/hpj/98may/ma98a2.pdf
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-10-10 18:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-04 14:38 MMIO regions James Simmons
1999-10-04 15:31 ` Stephen C. Tweedie
1999-10-04 15:52 ` James Simmons
1999-10-04 16:02 ` Benjamin C.R. LaHaise
1999-10-04 17:27 ` James Simmons
1999-10-04 17:56 ` Benjamin C.R. LaHaise
1999-10-04 18:26 ` James Simmons
1999-10-04 19:19 ` Stephen C. Tweedie
1999-10-06 20:15 ` James Simmons
1999-10-11 17:09 ` Stephen C. Tweedie
1999-10-11 17:26 ` Jeff Garzik
1999-10-11 23:14 ` James Simmons
1999-10-11 17:57 ` James Simmons
1999-10-04 16:11 ` Stephen C. Tweedie
1999-10-04 18:29 ` James Simmons
1999-10-04 19:35 ` Stephen C. Tweedie
1999-10-07 19:40 ` James Simmons
1999-10-10 11:24 ` Rik Faith
1999-10-10 14:03 ` Eric W. Biederman
1999-10-10 18:46 ` Rik Faith [this message]
1999-10-11 0:21 ` James Simmons
1999-10-11 10:59 ` Rik Faith
1999-10-11 3:38 ` Eric W. Biederman
1999-10-10 14:21 ` James Simmons
1999-10-11 17:22 ` Stephen C. Tweedie
1999-10-04 16:58 ` Marcus Sundberg
1999-10-04 18:27 ` James Simmons
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=14336.53971.896012.84699@light.alephnull.com \
--to=faith@precisioninsight.com \
--cc=ebiederm+eric@ccr.net \
--cc=jsimmons@edgeglobal.com \
--cc=linux-mm@kvack.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 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.