| commit | 11cbf4d7aea861e37067407ba7a660ea566c1593 | [log] [tgz] |
|---|---|---|
| author | Nicolai Hähnle <nicolai.haehnle@amd.com> | Wed Sep 07 10:50:14 2016 +0200 |
| committer | Nicolai Hähnle <nicolai.haehnle@amd.com> | Mon Sep 12 13:54:59 2016 +0200 |
| tree | 20eddeb7982c07dcde7ce6a40fafc8b4065a1cd1 | |
| parent | 480ac143df281fef762e30f92bccc3b89674fef8 [diff] |
winsys/amdgpu: use only one fence per BO The fence that is added to the BO during flush is guaranteed to be signaled after all the fences that were in the fences array of the BO before the flush, because those fences are added as dependencies for the submission (and all this happens atomically under the bo_fence_lock). Therefore, keeping only the last fence around is sufficient. Reviewed-by: Marek Olšák <marek.olsak@amd.com>