summaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorErico Nunes <nunes.erico@gmail.com>2019-05-21 01:42:29 +0300
committerQiang Yu <yuq825@gmail.com>2019-05-21 15:47:36 +0300
commit47ab14578263571228ce63e9417d96847693c7b4 (patch)
treea38bf78aac55ec7e8438e5b3e0696680910d01c0 /MAINTAINERS
parent3c6b8625dde82600fd03ad1fcba223f1303ee535 (diff)
downloadlinux-47ab14578263571228ce63e9417d96847693c7b4.tar.xz
drm/lima: add timeout to drm scheduler init
After "5918045c4ed4 drm/scheduler: rework job destruction", lima started to leak memory due to buffers not being destroyed after job execution in the drm scheduler. This started happening because the drm scheduler only destroyed buffers after cancelling the job timeout handler, and for lima this handler was never started as lima specified a MAX_SCHEDULE_TIMEOUT timeout. Lima seems to run well in its current state with a real timeout, so to make it more aligned with the other drivers from now on, let's use a real default timeout. This also fixes the observed memory leaks. The 500ms value was chosen as it is the current value for all other embedded gpu drivers using drm sched. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Signed-off-by: Qiang Yu <yuq825@gmail.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190520224229.21111-1-nunes.erico@gmail.com
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions