linux/drivers/gpu/drm/drm_lock.c, branch v3.0.5

drm: readd drm_lock_free in drm_unlock

2010-09-26T03:35:49Z

I've accidently killed a little bit too much in commit 1da3f87ebb7edb3e0b829ec4bbe5fb3d9d93986f Author: Daniel Vetter Date: Mon Aug 23 22:53:24 2010 +0200 drm: kill kernel_context_switch callbacks Note to self: Next time also test with AIGLX disabled. Reported-and-Tested-by: Andy Furniss Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=30374 Signed-off-by: Daniel Vetter Signed-off-by: Dave Airlie

drm: don't export dri1 locking functions

2010-08-29T23:39:00Z

Only used by ioctl, not by any in-tree drivers. Signed-off-by: Daniel Vetter Signed-off-by: Dave Airlie

drm: kill dma_ready callbacks

2010-08-29T23:38:12Z

Not used by any driver. So drop it. Signed-off-by: Daniel Vetter Signed-off-by: Dave Airlie

drm: kill kernel_context_switch callbacks

2010-08-29T23:37:56Z

Not used by any in-kernel driver. So drop it. Signed-off-by: Daniel Vetter Signed-off-by: Dave Airlie

drm: fix regression in drm locking since BKL removal.

2010-08-26T23:10:28Z

This locking path needs proper auditing but probably too late for changes at this point for 2.6.36, so lets go with the quick fix, which is to drop the lock around schedule. Reported-by: Andreas Schwab Signed-off-by: Dave Airlie

drm: Avoid client deadlocks when the master disappears.

2009-03-02T23:50:20Z

This is done by 1) Wake up lock waiters when we close the master file descriptor. Not when the master structure is removed, since the latter requires the waiters themselves to release the refcount on the master structure -> Deadlock. 2) Send a SIGTERM to all clients waiting for the lock. Normally these clients will get a SIGPIPE when the X server dies, but clients may also spin trying to grab the DRM lock, without getting any sort of notification. Signed-off-by: Thomas Hellstrom Signed-off-by: Dave Airlie

drm: Don't return ERESTARTSYS to user-space.

2009-03-02T23:49:46Z

That return code is for in-kernel use only. Use EINTR instead. Signed-off-by: Thomas Hellstrom Signed-off-by: Dave Airlie

drm: move to kref per-master structures.

2008-12-29T07:47:22Z

This is step one towards having multiple masters sharing a drm device in order to get fast-user-switching to work. It splits out the information associated with the drm master into a separate kref counted structure, and allocates this when a master opens the device node. It also allows the current master to abdicate (say while VT switched), and a new master to take over the hardware. It moves the Intel and radeon drivers to using the sarea from within the new master structures. Signed-off-by: Dave Airlie

drm: Remove infrastructure for supporting i915's vblank swapping.

2008-11-11T07:44:26Z

It's not used in any other drivers, and doesn't look like it will be from drm.git master. Signed-off-by: Eric Anholt Signed-off-by: Dave Airlie

drm/i915: hold dev->struct_mutex and DRM lock during vblank ring operations

2008-10-23T03:45:56Z

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 Signed-off-by: Eric Anholt Signed-off-by: Dave Airlie