diff options
| author | Christian König <christian.koenig@amd.com> | 2020-03-12 12:03:34 +0100 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2020-04-01 14:44:46 -0400 |
| commit | 82c416b13cb7d22b96ec0888b296a48dff8a09eb (patch) | |
| tree | 3dd05d2b0d90a0d10f20f3d36e383d56b6ca01a1 /drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | |
| parent | 9ec420d833413e39a46b5327ac27436e24d1ad12 (diff) | |
| download | linux-82c416b13cb7d22b96ec0888b296a48dff8a09eb.tar.bz2 | |
drm/amdgpu: fix and cleanup amdgpu_gem_object_close v4
The problem is that we can't add the clear fence to the BO
when there is an exclusive fence on it since we can't
guarantee the the clear fence will complete after the
exclusive one.
To fix this refactor the function and also add the exclusive
fence as shared to the resv object.
v2: fix warning
v3: add excl fence as shared instead
v4: squash in fix for fence handling in amdgpu_gem_object_close
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: xinhui pan <xinhui.pan@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c')
0 files changed, 0 insertions, 0 deletions