Change-Id: Id6039cb50b73bdf8a6df37e5383f4bea4ae737ed
Signed-off-by: Evan Quan
---
drivers/gpu/drm/amd/powerplay/hwmgr/hardwaremanager.c | 14 +++---
drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c | 4 ++--
drivers/gpu/drm/amd/powerplay/inc/hardwaremanager.h | 2 +-
3 files chan
Change-Id: Ia27af812631666d2c9d54da156fd3451bd738d4b
Signed-off-by: Evan Quan
---
drivers/gpu/drm/amd/powerplay/amd_powerplay.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/amd/powerplay/amd_powerplay.c
b/drivers/gpu/drm/amd/powerplay/amd_powerplay.c
index f3888dd..68482
Change-Id: Iea827bdd8346da1286da8928044fb564c22ca63b
Signed-off-by: Evan Quan
---
drivers/gpu/drm/amd/amdgpu/amdgpu_dpm.h| 4 ++--
drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c | 10 +-
drivers/gpu/drm/amd/include/kgd_pp_interface.h | 2 +-
drivers/gpu/drm/amd/powerplay/amd_pow
Change-Id: I30ea29aa85ab89c0017ecb4e0ab469db5ab5c103
Signed-off-by: Evan Quan
---
drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c
index 814329b..91f809e
From: Yue Hin Lau
Signed-off-by: Yue Hin Lau
Reviewed-by: Eric Bernstein
Acked-by: Harry Wentland
Signed-off-by: Alex Deucher
[dr...@endlessm.com: backport to 4.15]
Signed-off-by: Daniel Drake
---
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_dpp.h | 2 +-
drivers/gpu/drm/amd/display/
Is it possible that the test is broken? A test that allocates memory to
exhaustion may well trigger the OOM killer. A test can do that by using
malloc. Why not by using the graphics driver? The OOM killer does what
it's supposed to do, and kills the broken application.
As I understand it, this cha
The difference is that the OOM killer doesn't know of the pages an application
allocates through the driver.
This results in a bad decision which process to kill.
I had patches to fix this a long time ago on the list, but never found time to
clean them up and push them upstream.
Andrey is now