drm/amdgpu: Use the TGID for trace_amdgpu_vm_update_ptes
authorFriedrich Vock <friedrich.vock@gmx.de>
Thu, 2 Feb 2023 16:21:03 +0000 (17:21 +0100)
committerAlex Deucher <alexander.deucher@amd.com>
Thu, 9 Feb 2023 03:32:40 +0000 (22:32 -0500)
The pid field corresponds to the result of gettid() in userspace.
However, userspace cannot reliably attribute PTE events to processes
with just the thread id. This patch allows userspace to easily
attribute PTE update events to specific processes by comparing this
field with the result of getpid().

For attributing events to specific threads, the thread id is also
contained in the common fields of each trace event.

Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Friedrich Vock <friedrich.vock@gmx.de>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
drivers/gpu/drm/amd/amdgpu/amdgpu_vm_pt.c

index b5f3bba851db8646119abfccf1edac3e15a9d485..01e42bdd8e4e891c4b016905b46a32cee15b7a61 100644 (file)
@@ -974,7 +974,7 @@ int amdgpu_vm_ptes_update(struct amdgpu_vm_update_params *params,
                        trace_amdgpu_vm_update_ptes(params, frag_start, upd_end,
                                                    min(nptes, 32u), dst, incr,
                                                    upd_flags,
-                                                   vm->task_info.pid,
+                                                   vm->task_info.tgid,
                                                    vm->immediate.fence_context);
                        amdgpu_vm_pte_update_flags(params, to_amdgpu_bo_vm(pt),
                                                   cursor.level, pe_start, dst,