Thomas Hellstrom 040ac32048 drm: fix driver deadlock with AIGLX and reclaim_buffers_locked
Bugzilla Bug #9457

Add refcounting of user waiters to the DRM hardware lock, so that we can use
DRM_LOCK_CONT flag more conservatively.

Also add a kernel waiter refcount that if nonzero transfers the lock for the
kernel context when it is released. This is useful when waiting for idle and can be used for very simple fence object driver implementations for the new memory manager

Signed-off-by: Dave Airlie <airlied@linux.ie>
2007-03-23 13:28:33 +11:00
..
2006-04-23 18:26:40 +10:00
2007-03-11 12:07:17 +11:00
2006-02-02 19:37:46 +11:00
2006-03-19 18:56:12 +11:00
2007-03-11 12:07:17 +11:00
2006-12-08 08:28:44 -08:00
2007-03-11 12:07:16 +11:00
2006-04-05 18:12:18 +10:00
2007-03-11 12:08:18 +11:00
2005-09-25 14:28:13 +10:00
2006-12-11 18:28:45 +11:00
2007-03-11 12:08:15 +11:00
2007-03-19 08:52:17 +11:00
2005-09-25 14:28:13 +10:00
2005-09-25 14:28:13 +10:00
2005-09-25 14:28:13 +10:00
2005-09-25 14:28:13 +10:00
2006-12-07 15:53:31 +11:00
2006-12-08 08:28:44 -08:00
2005-09-25 14:28:13 +10:00
2006-10-24 21:52:23 +10:00
2006-12-08 08:28:44 -08:00
2005-09-25 14:28:13 +10:00
2005-09-25 14:28:13 +10:00
2005-09-25 14:28:13 +10:00
2006-12-08 08:28:44 -08:00
2006-03-19 19:12:10 +11:00
2006-12-19 17:49:08 +11:00
2006-12-19 17:49:08 +11:00
2005-09-25 14:28:13 +10:00
2006-10-25 09:40:40 -07:00
2006-09-22 05:32:31 +10:00
2006-09-22 05:32:33 +10:00
2005-09-25 14:28:13 +10:00
2007-02-12 09:48:30 -08:00
2006-01-10 19:53:54 +11:00
2007-02-08 13:24:25 +11:00
2007-02-08 13:24:25 +11:00
2005-11-12 21:52:46 +11:00

************************************************************
* For the very latest on DRI development, please see:      *
*     http://dri.freedesktop.org/                          *
************************************************************

The Direct Rendering Manager (drm) is a device-independent kernel-level
device driver that provides support for the XFree86 Direct Rendering
Infrastructure (DRI).

The DRM supports the Direct Rendering Infrastructure (DRI) in four major
ways:

    1. The DRM provides synchronized access to the graphics hardware via
       the use of an optimized two-tiered lock.

    2. The DRM enforces the DRI security policy for access to the graphics
       hardware by only allowing authenticated X11 clients access to
       restricted regions of memory.

    3. The DRM provides a generic DMA engine, complete with multiple
       queues and the ability to detect the need for an OpenGL context
       switch.

    4. The DRM is extensible via the use of small device-specific modules
       that rely extensively on the API exported by the DRM module.


Documentation on the DRI is available from:
    http://dri.freedesktop.org/wiki/Documentation
    http://sourceforge.net/project/showfiles.php?group_id=387
    http://dri.sourceforge.net/doc/

For specific information about kernel-level support, see:

    The Direct Rendering Manager, Kernel Support for the Direct Rendering
    Infrastructure
    http://dri.sourceforge.net/doc/drm_low_level.html

    Hardware Locking for the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/hardware_locking_low_level.html

    A Security Analysis of the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/security_low_level.html