From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: frattaroli.nicolas@gmail.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/scheduler: fix drm_sched_job_add_implicit_dependencies
Date: Tue, 19 Oct 2021 15:06:31 +0200 [thread overview]
Message-ID: <b60c6edd-f5ef-d814-cd6d-ae3186758203@gmail.com> (raw)
In-Reply-To: <YW67iLFQ7ttCT54O@phenom.ffwll.local>
Am 19.10.21 um 14:35 schrieb Daniel Vetter:
> On Tue, Oct 19, 2021 at 01:27:06PM +0200, Christian König wrote:
>> Trivial fix since we now need to grab a reference to the fence we have
>> added. Previously the dma_resv function where doing that for us.
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Fixes: 9c2ba265352a drm/scheduler: ("use new iterator in drm_sched_job_add_implicit_dependencies v2")
> Uh I completely missed checking for that. Did you review all other
> conversions you've pushed for this kind of bug?
Yeah, currently double checking that.
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Also
>
> Reported-by: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
> References: https://lore.kernel.org/dri-devel/2023306.UmlnhvANQh@archbook/
>
> It's important to credit bug reporters! Also upgrade to t-b if Nicolas
> gets around to testing quickly.
Yeah, the credit part is certainly correct. I just usually ask people
before adding their mail address to kernel commits because of the spam
you get :)
Cheers,
Christian.
>
> Cheers, Daniel
>
>> ---
>> drivers/gpu/drm/scheduler/sched_main.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/scheduler/sched_main.c b/drivers/gpu/drm/scheduler/sched_main.c
>> index 5bc5f775abe1..94fe51b3caa2 100644
>> --- a/drivers/gpu/drm/scheduler/sched_main.c
>> +++ b/drivers/gpu/drm/scheduler/sched_main.c
>> @@ -707,6 +707,9 @@ int drm_sched_job_add_implicit_dependencies(struct drm_sched_job *job,
>> ret = drm_sched_job_add_dependency(job, fence);
>> if (ret)
>> return ret;
>> +
>> + /* Make sure to grab an additional ref on the added fence */
>> + dma_fence_get(fence);
>> }
>> return 0;
>> }
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2021-10-19 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 11:27 [PATCH] drm/scheduler: fix drm_sched_job_add_implicit_dependencies Christian König
2021-10-19 12:35 ` Daniel Vetter
2021-10-19 13:06 ` Christian König [this message]
2021-10-19 13:25 ` Nicolas Frattaroli
2021-10-19 12:47 ` Nicolas Frattaroli
-- strict thread matches above, loose matches on Subject: below --
2021-11-16 4:23 Yassine Oudjana
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=b60c6edd-f5ef-d814-cd6d-ae3186758203@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=frattaroli.nicolas@gmail.com \
/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