On 22/01/25 22:24, Maíra Canal wrote:
In commit e4b5ccd392b9 ("drm/v3d: Ensure job pointer is set to NULL
after job completion"), we introduced a change to assign the job pointer
to NULL after completing a job, indicating job completion.
However, this approach created a race condition between th
Reviewed-by: Jose Maria Casanova Crespo
El 23/1/25 a las 2:24, Maíra Canal escribió:
In commit e4b5ccd392b9 ("drm/v3d: Ensure job pointer is set to NULL
after job completion"), we introduced a change to assign the job pointer
to NULL after completing a job, indicating job completion.
However,
Thanks for this, Maíra.
Tested-by: Phil Elwell
On Thu, 23 Jan 2025 at 07:12, Iago Toral wrote:
>
> Looks good to me:
>
> Reviewed-by: Iago Toral Quiroga
>
> El mié, 22-01-2025 a las 22:24 -0300, Maíra Canal escribió:
> > In commit e4b5ccd392b9 ("drm/v3d: Ensure job pointer is set to NULL
> > a
Looks good to me:
Reviewed-by: Iago Toral Quiroga
El mié, 22-01-2025 a las 22:24 -0300, Maíra Canal escribió:
> In commit e4b5ccd392b9 ("drm/v3d: Ensure job pointer is set to NULL
> after job completion"), we introduced a change to assign the job
> pointer
> to NULL after completing a job, indic
In commit e4b5ccd392b9 ("drm/v3d: Ensure job pointer is set to NULL
after job completion"), we introduced a change to assign the job pointer
to NULL after completing a job, indicating job completion.
However, this approach created a race condition between the DRM
scheduler workqueue and the IRQ ex
