diff options
author | 2023-01-12 10:12:43 +0100 | |
---|---|---|
committer | 2023-01-12 14:11:57 +0100 | |
commit | 07a2975c65f2be2e22591d795a9c39b00f95fd11 (patch) | |
tree | fd590449be5a9f6079029d4c7df97be2f0c32f91 /tools/perf/scripts/python | |
parent | drm: Optimize drm buddy top-down allocation method (diff) | |
download | wireguard-linux-07a2975c65f2be2e22591d795a9c39b00f95fd11.tar.xz wireguard-linux-07a2975c65f2be2e22591d795a9c39b00f95fd11.zip |
drm/vc4: bo: Fix drmm_mutex_init memory hog
Commit 374146cad469 ("drm/vc4: Switch to drmm_mutex_init") converted,
among other functions, vc4_create_object() to use drmm_mutex_init().
However, that function is used to allocate a BO, and therefore the
mutex needs to be freed much sooner than when the DRM device is removed
from the system.
For each buffer allocation we thus end up allocating a small structure
as part of the DRM-managed mechanism that is never freed, eventually
leading us to no longer having any free memory anymore.
Let's switch back to mutex_init/mutex_destroy to deal with it properly.
Fixes: 374146cad469 ("drm/vc4: Switch to drmm_mutex_init")
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
Link: https://patchwork.freedesktop.org/patch/msgid/20230112091243.490799-1-maxime@cerno.tech
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions