On Thu, 2005-11-24 at 10:52 +0100, Thomas Hellström wrote: > I made a fix to the locking code in main drm a couple of months ago. > > The X server tries to get the DRM_QUIESCENT lock, but when the wait > was interrupted by a signal (like when you move a window around), the > locking function returned without error. This made the X server > release other clients' locks. > > This does affect all drivers with a quiescent() function. Not only > via. > > But it looks like this fix never made it into the kernel source?
Thanks. BTW can you point me to a good explanation of DRM locking? There's so much indirection in the DRM code I can't even tell whether there's one DRM lock or several, what kind of lock it is or what it's protecting (beyond "access to the hardware"). Is it just an advisory lock used by DRM clients to keep from stepping on each other? It doesn't seem related to spinlocks or mutexes or any of the other types of lock in the kernel. Lee ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
