RE: [PATCH v3] drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap

2023-12-12 Thread Wang, Beyond
ut actually it is called after move happens, here the new_mem is same as bo->resource Fix: move trace_amdgpu_bo_move from move_notify to amdgpu_bo_move Signed-off-by: Wang, Beyond wang.bey...@amd.com<mailto:wang.bey...@amd.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 13 +

[PATCH v2] drm/amdgpu: fix ftrace event amdgpu_bo_move always move

2023-12-12 Thread Wang, Beyond
ut actually it is called after move happens, here the new_mem is same as bo->resource Fix: move trace_amdgpu_bo_move from move_notify to amdgpu_bo_move Signed-off-by: Wang, Beyond wang.bey...@amd.com<mailto:wang.bey...@amd.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 13 +

[PATCH 1/1] drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap

2023-12-10 Thread Wang, Beyond
race_amdgpu_bo_move', the comment says move_notify is called before move happens, but actually it is called after move happens, here the new_mem is same as bo->resource Fix: pass old_mem instead when calling amdgpu_bo_move_notify Signed-off-by: Wang, Beyond wang.bey...@amd.com<mailto: