diff options
| author | Chris Wilson <[email protected]> | 2018-07-19 07:22:06 +0000 |
|---|---|---|
| committer | Chris Wilson <[email protected]> | 2018-07-19 11:27:46 +0000 |
| commit | 46b1063f91e5680eff2a6b9fe432f6aae3bef54e (patch) | |
| tree | daf50db29b5d08e593ef226c396d1c4155431ab2 /drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | |
| parent | drm/i915/guc: Keep guc submission permanently engaged (diff) | |
| download | kernel-46b1063f91e5680eff2a6b9fe432f6aae3bef54e.tar.gz kernel-46b1063f91e5680eff2a6b9fe432f6aae3bef54e.zip | |
drm/i915: Handle recursive shrinker for vma->last_active allocation
If we call into the shrinker for direct relcaim inside kmalloc, it will
retire the requests. If we retire the vma->last_active while processing a
new i915_vma_move_to_active() we can upset the delicate bookkeeping
required for the cache. After the possible invocation of the shrinker, we
need to double check the vma->last_active is still valid.
Fixes: 8b293eb53a7d ("drm/i915: Track the last-active inside the i915_vma")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105600#c39
Signed-off-by: Chris Wilson <[email protected]>
Cc: Tvrtko Ursulin <[email protected]>
Reviewed-by: Tvrtko Ursulin <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c')
0 files changed, 0 insertions, 0 deletions