drm/xe: account for dontneed in fdinfo purgeable

Now that Xe supports explicit madvise WILLNEED/DONTNEED states,
userspace can mark memory in any placement as eligible for purging.
Update bo_meminfo to also include any BO explicitly marked as DONTNEED
in the purgeable statistics, ensuring fdinfo accurately reflects all
memory offered up for reclamation.

v2 (Sashiko):
  - Also update the drm_print_memory_stats() so we don't mask out !=
    SYSTEM

Assisted-by: Copilot:gemini-3.1-pro-preview
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Arvind Yadav <arvind.yadav@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Link: https://patch.msgid.link/20260625152054.450125-7-matthew.auld@intel.com
This commit is contained in:
Matthew Auld 2026-06-25 16:20:57 +01:00
parent c9a8e7daa0
commit cde38f5a5d

View File

@ -193,7 +193,7 @@ static void bo_meminfo(struct xe_bo *bo,
if (!dma_resv_test_signaled(bo->ttm.base.resv,
DMA_RESV_USAGE_BOOKKEEP))
stats[mem_type].active += sz;
else if (mem_type == XE_PL_SYSTEM)
else if (mem_type == XE_PL_SYSTEM || xe_bo_madv_is_dontneed(bo))
stats[mem_type].purgeable += sz;
}
}
@ -273,8 +273,7 @@ static void show_meminfo(struct drm_printer *p, struct drm_file *file)
&stats[mem_type],
DRM_GEM_OBJECT_ACTIVE |
DRM_GEM_OBJECT_RESIDENT |
(mem_type != XE_PL_SYSTEM ? 0 :
DRM_GEM_OBJECT_PURGEABLE),
DRM_GEM_OBJECT_PURGEABLE,
xe_mem_type_to_name[mem_type]);
}
}