Skip to content

Commit 73d10c7

Browse files
matt-auldlucasdemarchi
authored andcommitted
drm/xe/client: use mem_type from the current resource
Rather extract the mem_type from the current resource. Checking the first potential placement doesn't really tell us where the bo is currently allocated, especially if there are multiple potential placements. Signed-off-by: Matthew Auld <[email protected]> Cc: Himal Prasad Ghimiray <[email protected]> Cc: Tejas Upadhyay <[email protected]> Cc: "Thomas Hellström" <[email protected]> Reviewed-by: Matthew Brost <[email protected]> Reviewed-by: Tejas Upadhyay <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected] (cherry picked from commit fbd73b7) Signed-off-by: Lucas De Marchi <[email protected]>
1 parent 69bbe3a commit 73d10c7

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

drivers/gpu/drm/xe/xe_drm_client.c

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -168,15 +168,10 @@ static void bo_meminfo(struct xe_bo *bo,
168168
struct drm_memory_stats stats[TTM_NUM_MEM_TYPES])
169169
{
170170
u64 sz = bo->size;
171-
u32 mem_type;
171+
u32 mem_type = bo->ttm.resource->mem_type;
172172

173173
xe_bo_assert_held(bo);
174174

175-
if (bo->placement.placement)
176-
mem_type = bo->placement.placement->mem_type;
177-
else
178-
mem_type = XE_PL_TT;
179-
180175
if (drm_gem_object_is_shared_for_memory_stats(&bo->ttm.base))
181176
stats[mem_type].shared += sz;
182177
else

0 commit comments

Comments
 (0)