Re: [PATCH] gpu/drm/udl: Replace struct_mutex with driver private lock

2018-02-19 Thread Daniel Vetter
On Sat, Feb 10, 2018 at 06:47:31PM +0530, Shreeya Patel wrote: > On Fri, 2018-02-09 at 12:18 +, Chris Wilson wrote: > > Quoting Shreeya Patel (2018-02-09 12:10:56) > > > > > > dev->struct_mutex is the Big DRM Lock and the only bit where > > > it’s mandatory is serializing GEM buffer object des

Re: [PATCH] gpu/drm/udl: Replace struct_mutex with driver private lock

2018-02-10 Thread Shreeya Patel
On Fri, 2018-02-09 at 12:18 +, Chris Wilson wrote: > Quoting Shreeya Patel (2018-02-09 12:10:56) > > > > dev->struct_mutex is the Big DRM Lock and the only bit where > > it’s mandatory is serializing GEM buffer object destruction. > > Which unfortunately means drivers have to keep track of tha

Re: [PATCH] gpu/drm/udl: Replace struct_mutex with driver private lock

2018-02-09 Thread Chris Wilson
Quoting Shreeya Patel (2018-02-09 12:10:56) > dev->struct_mutex is the Big DRM Lock and the only bit where > it’s mandatory is serializing GEM buffer object destruction. > Which unfortunately means drivers have to keep track of that > lock and either call unreference or unreference_locked > dependi

[PATCH] gpu/drm/udl: Replace struct_mutex with driver private lock

2018-02-09 Thread Shreeya Patel
dev->struct_mutex is the Big DRM Lock and the only bit where it’s mandatory is serializing GEM buffer object destruction. Which unfortunately means drivers have to keep track of that lock and either call unreference or unreference_locked depending upon context. Core GEM doesn’t have a need for stru