linux/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c, branch v4.7

drm/amdgpu: fix bug in fence driver fini

2016-05-25T13:42:53Z

Using wrong counter for walking fences. Fixes a crash when unloading the driver. Signed-off-by: Monk Liu Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: create fence slab once when amdgpu module init.

2016-05-13T18:30:22Z

This avoids problems with multiple GPUs. For example, if the first GPU failed before amdgpu_fence_init() was called, amdgpu_fence_slab_ref is still 0 and it will get decremented in amdgpu_fence_driver_fini(). This will lead to a crash during init of the second GPU since amdgpu_fence_slab_ref is not 0. v2: add functions for init/exit instead of moving the variables into the driver. Signed-off-by: Rex Zhu Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: Replace rcu_assign_pointer() with RCU_INIT_POINTER()

2016-05-05T00:31:06Z

The rcu_assign_pointer() ensures that the initialization of a structure is carried out before storing a pointer to that structre. It is always safe to use RCU_INIT_POINTER() to NULL a pointer, instead of rcu_assign_pointer(). This results in slightly smaller/faster code. The following semantic patch was used: @@ @@ - rcu_assign_pointer + RCU_INIT_POINTER (..., NULL) Reviewed-by: Christian König Signed-off-by: Muhammad Falak R Wani Signed-off-by: Alex Deucher

drm/amdgpu: double fence slot

2016-05-05T00:22:48Z

we introduced vmid fence, so one hw submission could produce two fences. Signed-off-by: Chunming Zhou Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: Mark all instances of struct drm_info_list as const

2016-05-05T00:20:10Z

All these are compile time constand and the drm_debugfs_create/remove_files functions take a const pointer argument. Reviewed-by: Christian König Signed-off-by: Nils Wallménius Signed-off-by: Alex Deucher

drm/amdgpu: fence wait old rcu slot

2016-04-01T14:08:39Z

since the rcu slot was initialized to be num_hw_submission, if command submission doesn't use scheduler, this limitation will be invalid like uvd test. Signed-off-by: Chunming Zhou Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: switch back to 32bit hw fences v2

2016-03-16T22:00:10Z

We don't need to extend them to 64bits any more, so avoid the extra overhead. v2: update commit message. Signed-off-by: Christian König Acked-by: Alex Deucher Reviewed-by: Chunming Zhou

drm/amdgpu: remove amdgpu_fence_is_signaled

2016-03-16T22:00:01Z

It's just overhead to check the fence value when we signal them directly anyway. Signed-off-by: Christian König Acked-by: Alex Deucher Reviewed-by: Chunming Zhou

drm/amdgpu: drop the extra fence range check v2

2016-03-16T21:59:52Z

Amdgpu doesn't support using scratch registers for fences any more. So we won't see values like 0xdeadbeef as fence value any more. v2: reschedule timer even if no change detected Signed-off-by: Christian König Acked-by: Alex Deucher Reviewed-by: Chunming Zhou

drm/amdgpu: signal fences directly in amdgpu_fence_process

2016-03-16T21:59:41Z

Because of the scheduler we need to signal all fences immediately anyway, so try to avoid the waitqueue overhead. Signed-off-by: Christian König Acked-by: Alex Deucher Reviewed-by: Chunming Zhou