From: "Christian König" <christian.koenig@amd.com>
To: "Yadav, Arvind" <arvyadav@amd.com>,
Arvind Yadav <Arvind.Yadav@amd.com>,
andrey.grodzovsky@amd.com, shashank.sharma@amd.com,
amaranath.somalapuram@amd.com, Arunpravin.PaneerSelvam@amd.com,
sumit.semwal@linaro.org, gustavo@padovan.org, airlied@linux.ie,
daniel@ffwll.ch, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] drm/sched: Add callback and enable signaling on debug
Date: Mon, 5 Sep 2022 17:32:17 +0200 [thread overview]
Message-ID: <46ae09bb-2514-94b9-4497-e275bcc5f1ee@amd.com> (raw)
In-Reply-To: <5b84f7c1-99a6-02c8-2606-8986891a95b0@amd.com>
Am 05.09.22 um 15:46 schrieb Yadav, Arvind:
> On 9/5/2022 4:55 PM, Christian König wrote:
>> [SNIP]
>>
>> Am 05.09.22 um 12:56 schrieb Arvind Yadav:
>>> .release = drm_sched_fence_release_finished,
>>> };
>>> diff --git a/drivers/gpu/drm/scheduler/sched_main.c
>>> b/drivers/gpu/drm/scheduler/sched_main.c
>>> index e0ab14e0fb6b..140e3d8646e2 100644
>>> --- a/drivers/gpu/drm/scheduler/sched_main.c
>>> +++ b/drivers/gpu/drm/scheduler/sched_main.c
>>> @@ -961,7 +961,9 @@ static int drm_sched_main(void *param)
>>> s_fence->parent = dma_fence_get(fence);
>>> /* Drop for original kref_init of the fence */
>>> dma_fence_put(fence);
>>
>> Uff, not related to your patch but that looks wrong to me. The
>> reference can only be dropped after the call to
>> dma_fence_add_callback().
>>
> Shall I take care with this patch or I will submit separate one ?
Separate one. It's probably no big deal since we grab another reference
right before, but still quite some broken coding.
Thanks,
Christian.
>
>>> -
>>> +#ifdef CONFIG_DEBUG_FS
>>> + dma_fence_enable_sw_signaling(&s_fence->finished);
>>> +#endif
>>
>> This should always be called, independent of the config options set.
>>
>> Christian.
>
> sure, I will remove the Config check.
>
> ~arvind
>
>>
>>> r = dma_fence_add_callback(fence, &sched_job->cb,
>>> drm_sched_job_done_cb);
>>> if (r == -ENOENT)
>>
next prev parent reply other threads:[~2022-09-05 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 10:56 [PATCH 0/4] dma-buf: To check enable signaling before signaled Arvind Yadav
2022-09-05 10:56 ` [PATCH 1/4] dma-buf: Check status of enable-signaling bit on debug Arvind Yadav
2022-09-05 11:21 ` Christian König
2022-09-05 13:43 ` Yadav, Arvind
2022-09-05 16:39 ` Tvrtko Ursulin
2022-09-05 18:26 ` Christian König
2022-09-05 10:56 ` [PATCH 2/4] drm/sched: Add callback and enable signaling " Arvind Yadav
2022-09-05 11:25 ` Christian König
2022-09-05 13:46 ` Yadav, Arvind
2022-09-05 14:58 ` Yadav, Arvind
2022-09-05 15:32 ` Christian König [this message]
2022-09-05 10:56 ` [PATCH 3/4] dma-buf: " Arvind Yadav
2022-09-05 11:26 ` Christian König
2022-09-05 13:50 ` Yadav, Arvind
2022-09-05 10:56 ` [PATCH 4/4] " Arvind Yadav
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=46ae09bb-2514-94b9-4497-e275bcc5f1ee@amd.com \
--to=christian.koenig@amd.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=Arvind.Yadav@amd.com \
--cc=airlied@linux.ie \
--cc=amaranath.somalapuram@amd.com \
--cc=andrey.grodzovsky@amd.com \
--cc=arvyadav@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=shashank.sharma@amd.com \
--cc=sumit.semwal@linaro.org \
/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