linux/drivers/gpu/drm
Keith Packard 9e44af790f drm/i915: hold dev->struct_mutex and DRM lock during vblank ring operations
To synchronize clip lists with the X server, the DRM lock must be held while
looking at drawable clip lists. To synchronize with other ring access, the
ring mutex must be held while inserting commands into the ring.  Failure to
do the first resulted in easy visual corruption when moving windows, and the
second could have corrupted the ring with DRI2.

Grabbing the DRM lock involves using the DRM tasklet mechanism, grabbing the
ring mutex means potentially sleeping. Deal with both of these by always
running the tasklet from a work handler.

Also, protect from clip list changes since the vblank request was queued by
making sure the window has at least one rectangle while looking inside,
preventing oopses .

Signed-off-by: Keith Packard <keithp@keithp.com>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-10-23 13:45:56 +10:00
..
i810
i830
i915 drm/i915: hold dev->struct_mutex and DRM lock during vblank ring operations 2008-10-23 13:45:56 +10:00
mga drm: kill drm_device->irq 2008-10-18 07:10:53 +10:00
r128 drm: kill drm_device->irq 2008-10-18 07:10:53 +10:00
radeon radeon: fix PCI bus mastering support enables. 2008-10-18 07:10:54 +10:00
savage
sis SiS DRM: fix a pointer cast warning 2008-10-18 07:10:10 +10:00
tdfx
via drm: kill drm_device->irq 2008-10-18 07:10:53 +10:00
ati_pcigart.c
drm_agpsupport.c i915: Map status page cached for chips with GTT-based HWS location. 2008-10-18 07:10:53 +10:00
drm_auth.c
drm_bufs.c
drm_cache.c drm: wbinvd is cache coherent. 2008-10-18 07:10:53 +10:00
drm_context.c
drm_dma.c
drm_drawable.c drm: fix leak of cliprects in drm_rmdraw() 2008-10-23 13:42:26 +10:00
drm_drv.c drm: Add GEM ("graphics execution manager") to i915 driver. 2008-10-18 07:10:12 +10:00
drm_fops.c drm: Add GEM ("graphics execution manager") to i915 driver. 2008-10-18 07:10:12 +10:00
drm_gem.c DRM: Return -EBADF on bad object in flink, and return curent name if it exists. 2008-10-18 07:10:52 +10:00
drm_hashtab.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c drm: Remove two leaks of vblank reference count in error paths. 2008-10-23 13:42:27 +10:00
drm_lock.c drm/i915: hold dev->struct_mutex and DRM lock during vblank ring operations 2008-10-23 13:45:56 +10:00
drm_memory.c drm: Add GEM ("graphics execution manager") to i915 driver. 2008-10-18 07:10:12 +10:00
drm_mm.c drm: Add GEM ("graphics execution manager") to i915 driver. 2008-10-18 07:10:12 +10:00
drm_pci.c
drm_proc.c i915: Fix format string warnings on x86-64. 2008-10-23 13:42:27 +10:00
drm_scatter.c
drm_sman.c
drm_stub.c drm: kill drm_device->irq 2008-10-18 07:10:53 +10:00
drm_sysfs.c drm: fix sysfs error path. 2008-10-18 07:10:11 +10:00
drm_vm.c
Kconfig drm: make CONFIG_DRM depend on CONFIG_SHMEM. 2008-10-18 07:10:54 +10:00
Makefile drm: Add GEM ("graphics execution manager") to i915 driver. 2008-10-18 07:10:12 +10:00
README.drm

************************************************************
* 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