dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Maira Canal <mcanal@igalia.com>
To: Iago Toral <itoral@igalia.com>, Emma Anholt <emma@anholt.net>,
	Melissa Wen <mwen@igalia.com>, David Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/v3d: wait for all jobs to finish before unregistering
Date: Mon, 30 Oct 2023 09:42:16 -0300	[thread overview]
Message-ID: <0322fe29-d762-03e6-bfb5-de346c7b3b16@igalia.com> (raw)
In-Reply-To: <5a5fd75945b6446783171e870e0c9f157bba557e.camel@igalia.com>

Hi Iago,

On 10/30/23 09:20, Iago Toral wrote:
> El mar, 24-10-2023 a las 07:05 -0300, Maira Canal escribió:
>> Hi Iago,
>>
>> On 10/24/23 02:57, Iago Toral wrote:
>>> El lun, 23-10-2023 a las 07:58 -0300, Maíra Canal escribió:
>>>> Currently, we are only warning the user if the BIN or RENDER jobs
>>>> don't
>>>> finish before we unregister V3D. We must wait for all jobs to
>>>> finish
>>>> before unregistering. Therefore, warn the user if TFU or CSD jobs
>>>> are not done by the time the driver is unregistered.
>>>>
>>>> Signed-off-by: Maíra Canal <mcanal@igalia.com>
>>>> ---
>>>>    drivers/gpu/drm/v3d/v3d_gem.c | 2 ++
>>>>    1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/drivers/gpu/drm/v3d/v3d_gem.c
>>>> b/drivers/gpu/drm/v3d/v3d_gem.c
>>>> index 2e94ce788c71..afa7d170d1ff 100644
>>>> --- a/drivers/gpu/drm/v3d/v3d_gem.c
>>>> +++ b/drivers/gpu/drm/v3d/v3d_gem.c
>>>> @@ -1072,6 +1072,8 @@ v3d_gem_destroy(struct drm_device *dev)
>>>>            */
>>>>           WARN_ON(v3d->bin_job);
>>>>           WARN_ON(v3d->render_job);
>>>> +       WARN_ON(v3d->tfu_job);
>>>> +       WARN_ON(v3d->csd_job);
>>>
>>> I guess we should do this for cache clean jobs too, right?
>>
>> As the cache clean jobs are synchronous, we don't keep track of the
>> current cache clean job. When I say that the cache clean jobs are
>> synchronous, it means that the end of the job is not determined by
>> an interruption. Therefore, there is no need to make sure that the
>> cache clean jobs are still running.
> 
> I see, thanks Maíra.
> 
> Reviewed-by: Iago Toral Quiroga <itoral@igalia.com>

Applied to drm-misc/drm-misc-next!

Thanks,
- Maíra

> 
>>
>> Best Regards,
>> - Maíra
>>
>>>
>>> Iago
>>>
>>>>    
>>>>           drm_mm_takedown(&v3d->mm);
>>>>    
>>>
>>
> 

      reply	other threads:[~2023-10-30 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 10:58 [PATCH 1/2] drm/v3d: wait for all jobs to finish before unregistering Maíra Canal
2023-10-23 10:58 ` [PATCH 2/2] drm/v3d: assure that the job is NULL after being freed Maíra Canal
2023-10-24  5:57 ` [PATCH 1/2] drm/v3d: wait for all jobs to finish before unregistering Iago Toral
2023-10-24 10:05   ` Maira Canal
2023-10-30 12:20     ` Iago Toral
2023-10-30 12:42       ` Maira Canal [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=0322fe29-d762-03e6-bfb5-de346c7b3b16@igalia.com \
    --to=mcanal@igalia.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=itoral@igalia.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=mwen@igalia.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;
as well as URLs for NNTP newsgroup(s).