1. 03 2月, 2021 1 次提交
  2. 09 12月, 2020 1 次提交
  3. 04 12月, 2020 1 次提交
  4. 04 11月, 2020 2 次提交
  5. 16 10月, 2020 1 次提交
  6. 15 10月, 2020 1 次提交
  7. 07 10月, 2020 1 次提交
  8. 06 10月, 2020 1 次提交
  9. 28 9月, 2020 1 次提交
  10. 24 9月, 2020 1 次提交
  11. 11 9月, 2020 1 次提交
  12. 25 8月, 2020 1 次提交
  13. 18 8月, 2020 1 次提交
  14. 12 8月, 2020 1 次提交
  15. 06 8月, 2020 3 次提交
  16. 05 8月, 2020 1 次提交
  17. 25 6月, 2020 1 次提交
  18. 29 4月, 2020 1 次提交
  19. 11 3月, 2020 1 次提交
  20. 27 2月, 2020 3 次提交
  21. 05 2月, 2020 2 次提交
  22. 18 10月, 2019 1 次提交
  23. 17 10月, 2019 1 次提交
  24. 16 10月, 2019 1 次提交
  25. 03 10月, 2019 1 次提交
  26. 17 9月, 2019 1 次提交
  27. 16 9月, 2019 1 次提交
  28. 22 8月, 2019 1 次提交
  29. 13 8月, 2019 1 次提交
  30. 06 8月, 2019 2 次提交
  31. 05 8月, 2019 1 次提交
  32. 02 8月, 2019 1 次提交
    • F
      drm/amdgpu: Implement VRAM wipe on release · ab2f7a5c
      Felix Kuehling 提交于
      Wipe VRAM memory containing sensitive data when moving or releasing
      BOs. Clearing the memory is pipelined to minimize any impact on
      subsequent memory allocation latency. Use of a poison value should
      help debug future use-after-free bugs.
      
      When moving BOs, the existing ttm_bo_pipelined_move ensures that the
      memory won't be reused before being wiped.
      
      When releasing BOs, the BO is fenced with the memory fill operation,
      which results in queuing the BO for a delayed delete.
      
      v2: Move amdgpu_amdkfd_unreserve_memory_limit into
      amdgpu_bo_release_notify so that KFD can use memory that's still
      being cleared in the background
      Signed-off-by: NFelix Kuehling <Felix.Kuehling@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      ab2f7a5c
  33. 31 7月, 2019 1 次提交
    • D
      drm/amdgpu: Fill out gem_object->resv · b2ad978f
      Daniel Vetter 提交于
      That way we can ditch our gem_prime_res_obj implementation. Since ttm
      absolutely needs the right reservation object all the boilerplate is
      already there and we just have to wire it up correctly.
      
      Note that gem/prime doesn't care when we do this, as long as we do it
      before the bo is registered and someone can call the handle2fd ioctl
      on it.
      
      Aside: ttm_buffer_object.ttm_resv could probably be ditched in favour
      of always passing a non-NULL resv to ttm_bo_init(). At least for gem
      drivers that would avoid having two of these, on in ttm_buffer_object
      and the other in drm_gem_object, one just there for confusion.
      Acked-by: NGerd Hoffmann <kraxel@redhat.com>
      Cc: Gerd Hoffmann <kraxel@redhat.com>
      Reviewed-by: NEmil Velikov <emil.velikov@collabora.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
      Cc: Alex Deucher <alexander.deucher@amd.com>
      Cc: "Christian König" <christian.koenig@amd.com>
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Cc: "Michel Dänzer" <michel.daenzer@amd.com>
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Cc: Huang Rui <ray.huang@amd.com>
      Cc: Felix Kuehling <Felix.Kuehling@amd.com>
      Cc: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
      Cc: Evan Quan <evan.quan@amd.com>
      Cc: Sonny Jiang <sonny.jiang@amd.com>
      Cc: Amber Lin <Amber.Lin@amd.com>
      Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
      Cc: Junwei Zhang <Jerry.Zhang@amd.com>
      Cc: Thomas Zimmermann <contact@tzimmermann.org>
      Cc: Samuel Li <Samuel.Li@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190725132655.11951-4-daniel.vetter@ffwll.ch
      b2ad978f