diff options
| author | Jose Maria Casanova Crespo <jmcasanova@igalia.com> | 2026-11-01 09:53:57 -0300 |
|---|---|---|
| committer | Maíra Canal <mcanal@igalia.com> | 2026-11-02 09:46:35 -0300 |
| commit | 0afdbdd5b1af729108de8f893d179c3b99eac29d (patch) | |
| tree | b092842269302550e098a4a18ca288d0781c31eb /include/linux/zstd_errors.h | |
| parent | f00d7a241f846b053e89c0bb2285ef5988d4cafc (diff) | |
drm/v3d: Initialize timedout_batches when running a CSD job
v3d_csd_job_timedout() decides whether a compute job made progress by
comparing CSD_CURRENT_CFG4, the number of batches the dispatcher still
has to start, against the value saved at the previous timeout. That
saved value is never initialized, so it is zero on the first timeout.
On V3D 7.1.6 and later, CFG4 counts down to zero once the dispatcher has
started the last batch, but the dispatch keeps running until the batches
in flight complete. If the first timeout fires in that window, the
handler sees no change and resets the GPU while the job is about to
complete. For example, this happens with long dispatches that only keep a
single supergroup in flight.
Initialize timedout_batches to the value programmed in CFG4 when the job
is started. The register does not return to it once a batch has started:
it counts down to zero on V3D 7.1.6 and later (CFG4 holds the number of
batches), and to 0xffffffff on V3D 4.2 (CFG4 holds the number of batches
minus one).
Cc: stable@vger.kernel.org
Fixes: d223f98f0209 ("drm/v3d: Add support for compute shader dispatch.")
Signed-off-by: Jose Maria Casanova Crespo <jmcasanova@igalia.com>
Reviewed-by: Iago Toral Quiroga <itoral@igalia.com>
Link: https://patch.msgid.link/20261101125619.2465064-1-mcanal@igalia.com
Signed-off-by: Maíra Canal <mcanal@igalia.com>
Diffstat (limited to 'include/linux/zstd_errors.h')
0 files changed, 0 insertions, 0 deletions
