Yeah, adding dma_fence_enable_sw_signaling() is the right thing to do.
The question is where to add that? Usually right before the fence is
returned from the object or queried from userspace would probably be the
right place.
Regards,
Christian.
Am 12.07.22 um 16:22 schrieb Lionel Landwerlin:
I'll let Lucas comment. I've only looked a little at it.
From what I remember just enabling sw_signaling was enough to fix the
issue.
-Lionel
On 12/07/2022 13:26, Christian König wrote:
Ping to the Intel guys here. Especially Lucas/Nirmoy/Lionel.
IIRC you stumbled over that problem as well, have you found any
solution?
Regards,
Christian.
Am 07.07.22 um 12:29 schrieb jie1zhan:
enable signaling after flatten dma_fence_chains on transfer
Signed-off-by: jie1zhan <jesse.zhang@xxxxxxx>
---
drivers/gpu/drm/drm_syncobj.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/drm_syncobj.c
b/drivers/gpu/drm/drm_syncobj.c
index 7e48dcd1bee4..0d9d3577325f 100644
--- a/drivers/gpu/drm/drm_syncobj.c
+++ b/drivers/gpu/drm/drm_syncobj.c
@@ -920,6 +920,7 @@ static int
drm_syncobj_transfer_to_timeline(struct drm_file *file_private,
if (ret)
goto err_free_fence;
+ dma_fence_enable_sw_signaling(fence);
chain = dma_fence_chain_alloc();
if (!chain) {
ret = -ENOMEM;
