On ti, 2016-11-01 at 09:15 +0000, Chris Wilson wrote: > On Tue, Nov 01, 2016 at 11:10:31AM +0200, Joonas Lahtinen wrote: > > > > On ma, 2016-10-31 at 12:40 +0000, Chris Wilson wrote: > > As discussed in IRC, I think we rather should add a lock class to > > obj->mm, to avoid chasing these in the future. > > All ears :) The complicated one isn't obj->mm, but the timeline->lock. > That we may do engine1->tl->lock, engine2->tl->lock, request->tl->lock, > so far. Just realized we would have to properly reboot the kernel after each test not to run out of locking classes... For timeline->lock, the same thing. Just assign each timeline its own lock class. But no bonus until we reboot enough. Regards, Joonas -- Joonas Lahtinen Open Source Technology Center Intel Corporation _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
