On Wed, Apr 18, 2012 at 07:06:10PM +0300, Ville Syrjälä wrote: > On Wed, Apr 18, 2012 at 05:27:57PM +0200, Daniel Vetter wrote: > > Also, I'm toying around with ideas to split up the big modeset lock such > > that operations that only touch the crtc (like pageflip, plane changes and > > cursor changes) do not take the big modeset lock but only a per-crtc > > mutex. > > Plane operations might well involve multiple CRTCs (when moving the > planes between pipes for example). You have to be careful with the > locking order when doing stuff like that. One option would be to > always take the per-CRTC locks in the same order (based on the > object ID for example). Multiple locks will also cause problems for the atomic mode set. The full device state may be needed to evaluate whether a certain change is allowed, which means any change happening in parallel can screw things up. -- Ville Syrjälä Intel OTC _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
