Thomas Hellstrom 05efb1abec drm/ttm: ttm object security fixes for render nodes ... When a client looks up a ttm object, don't look it up through the device hash table, but rather from the file hash table. That makes sure that the client has indeed put a reference on the object, or in gem terms, has opened the object; either using prime or using the global "name". To avoid a performance loss, make sure the file hash table entries can be looked up from under an RCU lock, and as a consequence, replace the rwlock with a spinlock, since we never need to take it in read mode only anymore. Finally add a ttm object lookup function for the device hash table, that is intended to be used when we put a ref object on a base object or, in gem terms, when we open the object. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Brian Paul <brianp@vmware.com>		2014-01-08 10:11:57 +01:00
..
ttm_bo_api.h
ttm_bo_driver.h
ttm_execbuf_util.h
ttm_lock.h
ttm_memory.h
ttm_module.h
ttm_object.h	drm/ttm: ttm object security fixes for render nodes	2014-01-08 10:11:57 +01:00
ttm_page_alloc.h
ttm_placement.h