panfrost: Reset syncobj after use to avoid kernel warnings
We get a kernel message "You are adding an unorder point to timeline!"
on many CTS runs. This stems from us SIGNALing the queue syncobj then
WAITing but not reseting it. It is assumed by the time we get to
panvk_queue_submit_init_signals() that the value is 0, however it is 1
due to the previous calls.
Signed-off-by: Ashley Smith <ashley.smith@collabora.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Fixes: 5544d39f ("panvk: Add a CSF backend for panvk_queue/cmd_buffer")
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33943>
This commit is contained in:
@@ -474,6 +474,8 @@ init_subqueue(struct panvk_queue *queue, enum panvk_subqueue_id subqueue)
|
||||
return panvk_errorf(dev->vk.physical, VK_ERROR_INITIALIZATION_FAILED,
|
||||
"SyncobjWait failed: %m");
|
||||
|
||||
drmSyncobjReset(dev->vk.drm_fd, &queue->syncobj_handle, 1);
|
||||
|
||||
if (debug & PANVK_DEBUG_TRACE) {
|
||||
pandecode_user_msg(dev->debug.decode_ctx, "Init subqueue %d binary\n\n",
|
||||
subqueue);
|
||||
|
||||
Reference in New Issue
Block a user