1. 28 3月, 2014 1 次提交
  2. 08 1月, 2014 1 次提交
    • T
      drm/ttm: ttm object security fixes for render nodes · 05efb1ab
      Thomas Hellstrom 提交于
      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: NThomas Hellstrom <thellstrom@vmware.com>
      Reviewed-by: NBrian Paul <brianp@vmware.com>
      05efb1ab
  3. 18 11月, 2013 1 次提交
  4. 20 11月, 2012 1 次提交
  5. 03 10月, 2012 1 次提交
  6. 21 6月, 2011 1 次提交
  7. 15 12月, 2009 1 次提交
  8. 07 12月, 2009 1 次提交