All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oak Zeng <oak.zeng@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Thomas.Hellstrom@linux.intel.com, rodrigo.vivi@intel.com
Subject: [PATCH 3/3] drm/xe: Print vm parameter in xe_vma trace
Date: Wed, 18 Dec 2024 11:48:33 -0500	[thread overview]
Message-ID: <20241218164833.2364049-4-oak.zeng@intel.com> (raw)
In-Reply-To: <20241218164833.2364049-1-oak.zeng@intel.com>

Print the vm that the vma belongs to in the vma trace.
This is useful to correlate VMA operations to the VM.

Signed-off-by: Oak Zeng <oak.zeng@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_trace_bo.h | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_trace_bo.h b/drivers/gpu/drm/xe/xe_trace_bo.h
index a46f7cfd92c6f..ce4d0d7e81017 100644
--- a/drivers/gpu/drm/xe/xe_trace_bo.h
+++ b/drivers/gpu/drm/xe/xe_trace_bo.h
@@ -92,6 +92,7 @@ DECLARE_EVENT_CLASS(xe_vma,
 		    TP_STRUCT__entry(
 			     __string(dev, __dev_name_vma(vma))
 			     __field(struct xe_vma *, vma)
+			     __field(struct xe_vm *, vm)
 			     __field(u32, asid)
 			     __field(u64, start)
 			     __field(u64, end)
@@ -101,14 +102,16 @@ DECLARE_EVENT_CLASS(xe_vma,
 		    TP_fast_assign(
 			   __assign_str(dev);
 			   __entry->vma = vma;
+			   __entry->vm = xe_vma_vm(vma);
 			   __entry->asid = xe_vma_vm(vma)->usm.asid;
 			   __entry->start = xe_vma_start(vma);
 			   __entry->end = xe_vma_end(vma) - 1;
 			   __entry->ptr = xe_vma_userptr(vma);
 			   ),
 
-		    TP_printk("dev=%s, vma=%p, asid=0x%05x, start=0x%012llx, end=0x%012llx, userptr=0x%012llx,",
-			      __get_str(dev), __entry->vma, __entry->asid, __entry->start,
+		    TP_printk("dev=%s, vma=%p, vm=%p, asid=0x%05x, start=0x%012llx, end=0x%012llx, userptr=0x%012llx",
+			      __get_str(dev), __entry->vma, __entry->vm,
+			      __entry->asid, __entry->start,
 			      __entry->end, __entry->ptr)
 )
 
-- 
2.26.3


  parent reply	other threads:[~2024-12-18 16:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 16:48 [PATCH 0/3] drm/xe: Small trace print improvements Oak Zeng
2024-12-18 16:48 ` [PATCH 1/3] drm/xe: trace bo create Oak Zeng
2024-12-23 10:24   ` Ghimiray, Himal Prasad
2024-12-18 16:48 ` [PATCH 2/3] drm/xe: Print vm flags in xe_vm trace print Oak Zeng
2024-12-23 10:25   ` Ghimiray, Himal Prasad
2024-12-18 16:48 ` Oak Zeng [this message]
2024-12-23 10:26   ` [PATCH 3/3] drm/xe: Print vm parameter in xe_vma trace Ghimiray, Himal Prasad
2024-12-18 23:34 ` ✓ CI.Patch_applied: success for drm/xe: Small trace print improvements (rev2) Patchwork
2024-12-18 23:34 ` ✓ CI.checkpatch: " Patchwork
2024-12-18 23:35 ` ✓ CI.KUnit: " Patchwork
2024-12-18 23:53 ` ✓ CI.Build: " Patchwork
2024-12-18 23:55 ` ✓ CI.Hooks: " Patchwork
2024-12-18 23:57 ` ✓ CI.checksparse: " Patchwork
2024-12-19  0:30 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-19 16:59 ` ✗ Xe.CI.Full: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-12-17 23:14 [PATCH 0/3] drm/xe: Small trace print improvements Oak Zeng
2024-12-17 23:14 ` [PATCH 3/3] drm/xe: Print vm parameter in xe_vma trace Oak Zeng
2024-12-18  3:09   ` Matthew Brost
2024-11-28 22:09 [PATCH 1/3] drm/xe: trace bo create Oak Zeng
2024-11-28 22:09 ` [PATCH 3/3] drm/xe: Print vm parameter in xe_vma trace Oak Zeng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241218164833.2364049-4-oak.zeng@intel.com \
    --to=oak.zeng@intel.com \
    --cc=Thomas.Hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.