[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ea892ffc-4a03-7772-6d99-85a356a3738b@intel.com>
Date: Tue, 12 Jul 2022 17:22:03 +0300
From: Lionel Landwerlin <lionel.g.landwerlin@...el.com>
To: Christian König <christian.koenig@....com>,
jie1zhan <jesse.zhang@....com>, broonie@...nel.org,
dri-devel-bounces@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org
Cc: Vijendar.Mukunda@....com, Basavaraj.Hiregoudar@....com,
Sunil-kumar.Dommati@....com, ajitkumar.pandey@....com,
lucas.demarchi@...el.com, nirmoy.das@...ux.intel.com,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] drm/syncobj: Fix sync syncobj issue
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@....com>
>> ---
>> 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;
>
Powered by blists - more mailing lists