23 Nov
2015
23 Nov
'15
10 a.m.
Hi,
On 23 November 2015 at 09:32, Daniel Vetter daniel.vetter@ffwll.ch wrote:
The only things this protects is reading ->flags and ->size, both of which are invariant over the lifetime of an exynos gem bo. So no locking needed at all (besides that, nothing protects the writers anyway).
Aside: exynos_gem_obj->size is redundant with exynos_gem_obj->base.size and probably should be removed.
v2: Use _unlocked unreference (Daniel Stone).
Cc: Daniel Stone daniel@fooishbar.org Cc: Inki Dae inki.dae@samsung.com Signed-off-by: Daniel Vetter daniel.vetter@intel.com
Reviewed-by: Daniel Stone daniels@collabora.com
Cheers, Daniel