On Tue, Oct 22, 2019 at 03:30:13PM +0100, Matthew Auld wrote: > On Mon, 21 Oct 2019 at 09:03, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > > > > Separate each object class into a separate lock type to avoid lockdep > > cross-contamination between paths (i.e. userptr!). > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > Cc: Matthew Auld <matthew.auld@xxxxxxxxx> > > As per the explanation you gave on IRC, makes sense. > Reviewed-by: Matthew Auld <matthew.auld@xxxxxxxxx> It would be really lovely if such explanations would make it from ephemeral irc onto something more permanent like mailing lists, or even better, commit messages :-) So, why do we need this? I'm wondering since aside from userptr we'll have to unify how locking for bo works longer term (with all the dma_buf/ww_mutex stuff going on), not make it more distinct. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
