On Wed, May 02, 2012 at 10:22:33PM +0100, Chris Wilson wrote: > On Wed, 2 May 2012 23:12:36 +0200, Daniel Vetter <dan...@ffwll.ch> wrote: > > For consistency I guess we can ditch the dev parameter (and even then, the > > ring would uniquely identify the device). Also, I guess you need to > > explicitly pass in blocking, because mutex_is_locked is rather racy - > > someone else could hold the mutex while we're waiting in a non-blocking > > fashion. > > Meh, I suggested the race - I'd rather have a moment of confusion > reading the trace than reading the code in 6 months time.
Ok, I see the problem and agree, let's have it slightly racy ... -Daniel -- Daniel Vetter Mail: dan...@ffwll.ch Mobile: +41 (0)79 365 57 48 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
