[PATCH 4/5] drm/omapdrm: Fix mm_list locking
Tomi Valkeinen
tomi.valkeinen at ti.com
Thu Mar 29 09:40:23 UTC 2018
On 27/03/18 11:23, Daniel Vetter wrote:
> - None of the list walkings where protected.
>
> - Switch to a mutex since the list walking could potentially take a
> very long time.
>
> Only thing we need to be careful with here is that while we walk the
> list we cant unreference any gem objects, since the final unref would
> result in a recursive deadlock. But the only functions that walk the
> list is the device resume and debugfs dumping, so all safe.
>
> Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>
> Cc: Tomi Valkeinen <tomi.valkeinen at ti.com>
> ---
> drivers/gpu/drm/omapdrm/omap_debugfs.c | 2 ++
> drivers/gpu/drm/omapdrm/omap_drv.c | 2 +-
> drivers/gpu/drm/omapdrm/omap_drv.h | 2 +-
> drivers/gpu/drm/omapdrm/omap_gem.c | 11 +++++++----
> 4 files changed, 11 insertions(+), 6 deletions(-)
Thanks, I'll pick this to omapdrm branch.
Tomi
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
More information about the dri-devel
mailing list