iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

drm/xe: Enable D3Cold on 'low' VRAM utilization

Browse Source 
Now that we eliminated all the mem_access get/put with its
locking issues from the inner calls of migration, we can
allow D3Cold.

Enable it when VRAM utilization is lower then 300Mb. On
higher utilization we only allow D3hot so we don't increase
so much the latency on runtime resume due to the memory
restoration.

Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240522170105.327472-7-rodrigo.vivi@intel.com
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
This commit is contained in:
Rodrigo Vivi 2024-05-22 13:01:05 -04:00
parent 8d490e019b
commit f91806033f
No known key found for this signature in database
GPG Key ID: FA625F640EEB13CA
1 changed files with 1 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
drivers/gpu/drm/xe/xe_pm.h
View File

@ -8,12 +8,7 @@
#include <linux/pm_runtime.h>
/*
* TODO: Threshold = 0 will block D3Cold.
* Before we can move this to a higher value (like 300), we need to:
* 1. rewrite the VRAM save / restore to avoid buffer object locks
*/
#define DEFAULT_VRAM_THRESHOLD 0 /* in MB */
#define DEFAULT_VRAM_THRESHOLD 300 /* in MB */
struct xe_device;