ae358dacd2
It's only used to protect our page list, and only when we know we have a full reference. This means none of these code paths can ever race with the final unref, and hence we do not need dev->struct_mutex serialization and can simply switch to our own locking. For more context the only magic the locked gem_free_object provides is that it prevents concurrent final unref (and destruction) of gem objects while anyone is holding dev->struct_mutex. This was used by i915 (and other drivers) to implement eviction handling with less headaches. Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Cc: Dave Airlie <airlied@redhat.com> Reviewed-by: Sean Paul <seanpaul@chromium.org> Link: https://patchwork.freedesktop.org/patch/msgid/20180327082356.24516-3-daniel.vetter@ffwll.ch |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| udl_connector.c | ||
| udl_connector.h | ||
| udl_dmabuf.c | ||
| udl_drv.c | ||
| udl_drv.h | ||
| udl_encoder.c | ||
| udl_fb.c | ||
| udl_gem.c | ||
| udl_main.c | ||
| udl_modeset.c | ||
| udl_transfer.c | ||