Hi, On 23 November 2015 at 09:32, Daniel Vetter <daniel.vet...@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 <dan...@fooishbar.org> > Cc: Inki Dae <inki....@samsung.com> > Signed-off-by: Daniel Vetter <daniel.vet...@intel.com>
Reviewed-by: Daniel Stone <dani...@collabora.com> Cheers, Daniel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
