The changes to fix those are two invasive for backporting.
Just disable the feature in 4.20 and 5.0.
Signed-off-by: Christian König christian.koenig@amd.com Cc: stable@vger.kernel.org [4.20+] --- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c index 0877ff9a9594..c3643dde3e9d 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c @@ -637,12 +637,14 @@ void amdgpu_vm_move_to_lru_tail(struct amdgpu_device *adev, struct ttm_bo_global *glob = adev->mman.bdev.glob; struct amdgpu_vm_bo_base *bo_base;
+#if 0 if (vm->bulk_moveable) { spin_lock(&glob->lru_lock); ttm_bo_bulk_move_lru_tail(&vm->lru_bulk_move); spin_unlock(&glob->lru_lock); return; } +#endif
memset(&vm->lru_bulk_move, 0, sizeof(vm->lru_bulk_move));
On Wed, Feb 20, 2019 at 03:16:06PM +0100, Christian König wrote:
The changes to fix those are two invasive for backporting.
Just disable the feature in 4.20 and 5.0.
Signed-off-by: Christian König christian.koenig@amd.com Cc: stable@vger.kernel.org [4.20+]
For the sake of having it in the log, could you point to the upstream commit(s) that fix it?
-- Thanks, Sasha
Am 21.02.19 um 04:09 schrieb Sasha Levin:
On Wed, Feb 20, 2019 at 03:16:06PM +0100, Christian König wrote:
The changes to fix those are two invasive for backporting.
Just disable the feature in 4.20 and 5.0.
Signed-off-by: Christian König christian.koenig@amd.com Cc: stable@vger.kernel.org [4.20+]
For the sake of having it in the log, could you point to the upstream commit(s) that fix it?
That turned out to be a larger set of patches and won't go upstream before the 5.1 cycle.
Christian.
-- Thanks, Sasha
linux-stable-mirror@lists.linaro.org