Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 31 1月, 2020 1 次提交
  3. 22 1月, 2020 1 次提交
  5. 28 12月, 2019 1 次提交
  7. 26 12月, 2019 1 次提交
  9. 22 12月, 2019 1 次提交
  11. 09 12月, 2019 1 次提交
  13. 04 12月, 2019 1 次提交
  15. 03 12月, 2019 1 次提交
  17. 20 11月, 2019 1 次提交
  19. 14 11月, 2019 2 次提交
  21. 13 11月, 2019 1 次提交
  23. 08 11月, 2019 1 次提交
  25. 06 11月, 2019 1 次提交
    • I
      drm/i915/gen8+: Add RC6 CTX corruption WA · 7e34f4e4
      由 Imre Deak 提交于 
      In some circumstances the RC6 context can get corrupted. We can detect
this and take the required action, that is disable RC6 and runtime PM.
The HW recovers from the corrupted state after a system suspend/resume
cycle, so detect the recovery and re-enable RC6 and runtime PM.

v2: rebase (Mika)
v3:
- Move intel_suspend_gt_powersave() to the end of the GEM suspend
  sequence.
- Add commit message.
v4:
- Rebased on intel_uncore_forcewake_put(i915->uncore, ...) API
  change.
v5: rebased on gem/gt split (Mika)
Signed-off-by: NImre Deak <imre.deak@intel.com>
Signed-off-by: NMika Kuoppala <mika.kuoppala@linux.intel.com>
      7e34f4e4
  27. 05 11月, 2019 2 次提交
  29. 01 11月, 2019 3 次提交
  31. 27 10月, 2019 2 次提交
  33. 24 10月, 2019 1 次提交
  35. 22 10月, 2019 2 次提交
  37. 19 10月, 2019 1 次提交
  39. 18 10月, 2019 1 次提交
  41. 17 10月, 2019 1 次提交
  43. 08 10月, 2019 1 次提交
  45. 06 10月, 2019 2 次提交
  47. 04 10月, 2019 2 次提交
    • C
      drm/i915: Move context management under GEM · a4e7ccda
      由 Chris Wilson 提交于 
      Keep track of the GEM contexts underneath i915->gem.contexts and assign
them their own lock for the purposes of list management.

v2: Focus on lock tracking; ctx->vm is protected by ctx->mutex
v3: Correct split with removal of logical HW ID
Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: NTvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20191004134015.13204-15-chris@chris-wilson.co.uk
      a4e7ccda
    • C
      drm/i915: Pull i915_vma_pin under the vm->mutex · 2850748e
      由 Chris Wilson 提交于 
      Replace the struct_mutex requirement for pinning the i915_vma with the
local vm->mutex instead. Note that the vm->mutex is tainted by the
shrinker (we require unbinding from inside fs-reclaim) and so we cannot
allocate while holding that mutex. Instead we have to preallocate
workers to do allocate and apply the PTE updates after we have we
reserved their slot in the drm_mm (using fences to order the PTE writes
with the GPU work and with later unbind).

In adding the asynchronous vma binding, one subtle requirement is to
avoid coupling the binding fence into the backing object->resv. That is
the asynchronous binding only applies to the vma timeline itself and not
to the pages as that is a more global timeline (the binding of one vma
does not need to be ordered with another vma, nor does the implicit GEM
fencing depend on a vma, only on writes to the backing store). Keeping
the vma binding distinct from the backing store timelines is verified by
a number of async gem_exec_fence and gem_exec_schedule tests. The way we
do this is quite simple, we keep the fence for the vma binding separate
and only wait on it as required, and never add it to the obj->resv
itself.

Another consequence in reducing the locking around the vma is the
destruction of the vma is no longer globally serialised by struct_mutex.
A natural solution would be to add a kref to i915_vma, but that requires
decoupling the reference cycles, possibly by introducing a new
i915_mm_pages object that is own by both obj->mm and vma->pages.
However, we have not taken that route due to the overshadowing lmem/ttm
discussions, and instead play a series of complicated games with
trylocks to (hopefully) ensure that only one destruction path is called!

v2: Add some commentary, and some helpers to reduce patch churn.
Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: NTvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20191004134015.13204-4-chris@chris-wilson.co.uk
      2850748e
  49. 02 10月, 2019 1 次提交
  51. 28 9月, 2019 1 次提交
  53. 23 9月, 2019 4 次提交
  55. 16 9月, 2019 1 次提交
  57. 12 9月, 2019 1 次提交