* [PATCH] drm/amdgpu: Remove fence_process in count_emitted
@ 2022-09-23 13:27 jiadong.zhu
2022-09-26 6:50 ` Christian König
0 siblings, 1 reply; 2+ messages in thread
From: jiadong.zhu @ 2022-09-23 13:27 UTC (permalink / raw)
To: amd-gfx; +Cc: Jiadong.Zhu
From: "Jiadong.Zhu" <Jiadong.Zhu@amd.com>
The function amdgpu_fence_count_emitted used in work_hander should not call
amdgpu_fence_process which must be used in irq handler.
Signed-off-by: Jiadong.Zhu <Jiadong.Zhu@amd.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
index d16c8c1f72db..790f7bfdc654 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
@@ -394,7 +394,6 @@ unsigned amdgpu_fence_count_emitted(struct amdgpu_ring *ring)
/* We are not protected by ring lock when reading the last sequence
* but it's ok to report slightly wrong fence count here.
*/
- amdgpu_fence_process(ring);
emitted = 0x100000000ull;
emitted -= atomic_read(&ring->fence_drv.last_seq);
emitted += READ_ONCE(ring->fence_drv.sync_seq);
--
2.25.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] drm/amdgpu: Remove fence_process in count_emitted
2022-09-23 13:27 [PATCH] drm/amdgpu: Remove fence_process in count_emitted jiadong.zhu
@ 2022-09-26 6:50 ` Christian König
0 siblings, 0 replies; 2+ messages in thread
From: Christian König @ 2022-09-26 6:50 UTC (permalink / raw)
To: jiadong.zhu, amd-gfx
Am 23.09.22 um 15:27 schrieb jiadong.zhu@amd.com:
> From: "Jiadong.Zhu" <Jiadong.Zhu@amd.com>
>
> The function amdgpu_fence_count_emitted used in work_hander should not call
> amdgpu_fence_process which must be used in irq handler.
>
> Signed-off-by: Jiadong.Zhu <Jiadong.Zhu@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> index d16c8c1f72db..790f7bfdc654 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
> @@ -394,7 +394,6 @@ unsigned amdgpu_fence_count_emitted(struct amdgpu_ring *ring)
> /* We are not protected by ring lock when reading the last sequence
> * but it's ok to report slightly wrong fence count here.
> */
> - amdgpu_fence_process(ring);
> emitted = 0x100000000ull;
> emitted -= atomic_read(&ring->fence_drv.last_seq);
> emitted += READ_ONCE(ring->fence_drv.sync_seq);
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-09-26 6:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-09-23 13:27 [PATCH] drm/amdgpu: Remove fence_process in count_emitted jiadong.zhu
2022-09-26 6:50 ` Christian König
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox