From: "Christian König" <christian.koenig@amd.com>
To: "Das, Nirmoy" <nirmoy.das@linux.intel.com>,
jie1zhan <jesse.zhang@amd.com>,
broonie@kernel.org, dri-devel-bounces@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: Vijendar.Mukunda@amd.com, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, ajitkumar.pandey@amd.com,
lucas.demarchi@intel.com, lionel.g.landwerlin@intel.com,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drm/syncobj: Fix sync syncobj issue
Date: Wed, 13 Jul 2022 11:15:59 +0200 [thread overview]
Message-ID: <9aa8538b-d535-4de5-6e07-fd81d2b3db33@amd.com> (raw)
In-Reply-To: <43192086-b9a6-387c-4a29-ea28aa65a3b4@linux.intel.com>
Am 13.07.22 um 10:42 schrieb Das, Nirmoy:
> Hi Christian,
>
> On 7/12/2022 12:26 PM, 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?
>
> I might be wrong but I think you are talking about
> igt@syncobj_timeline@transfer-timeline-point testcase which seems to be
>
> green in CI now
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fintel-gfx-ci.01.org%2Ftree%2Fdrm-tip%2Figt%40syncobj_timeline%40transfer-timeline-point.html&data=05%7C01%7Cchristian.koenig%40amd.com%7C722fc33842734ef5c05108da64abac60%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637932985747614383%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=q8JygSVZfGA8cEZn%2BdxVXX79pkpXRjZTS8kBQ6Lq%2Bmw%3D&reserved=0
>
> Lucas found out that the issues got fixed after ec8d985ff26f ("drm:
> use dma_fence_unwrap_merge() in drm_syncobj")
Yeah, but that's just coincident. The original bug that we fail to
enable signaling in the syncobj is still there.
No that this is any major problem, but it would still be nice to have
that fixed.
Regards,
Christian.
>
>
> Regards,
>
> Nirmoy
>
>>
>> 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@amd.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;
>>
prev parent reply other threads:[~2022-07-13 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 10:29 [PATCH v2] drm/syncobj: Fix sync syncobj issue jie1zhan
2022-07-12 10:26 ` Christian König
2022-07-12 14:22 ` Lionel Landwerlin
2022-07-12 14:57 ` Christian König
2022-07-13 8:42 ` Das, Nirmoy
2022-07-13 9:15 ` Christian König [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9aa8538b-d535-4de5-6e07-fd81d2b3db33@amd.com \
--to=christian.koenig@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=airlied@linux.ie \
--cc=ajitkumar.pandey@amd.com \
--cc=broonie@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.zhang@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nirmoy.das@linux.intel.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox