Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH 1/3] drm/xe/trace: improve xe_sched_msg trace
Date: Fri, 22 Nov 2024 16:19:15 +0000	[thread overview]
Message-ID: <20241122161914.321263-4-matthew.auld@intel.com> (raw)

Also include the gt_id, that way we can ignore duplicate guc_id across
different GTs when applying some filtering.

Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_trace.h | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/xe/xe_trace.h b/drivers/gpu/drm/xe/xe_trace.h
index de682978c4bf..d5281de04d54 100644
--- a/drivers/gpu/drm/xe/xe_trace.h
+++ b/drivers/gpu/drm/xe/xe_trace.h
@@ -284,6 +284,7 @@ DECLARE_EVENT_CLASS(xe_sched_msg,
 			     __string(dev, __dev_name_eq(((struct xe_exec_queue *)msg->private_data)))
 			     __field(u32, opcode)
 			     __field(u16, guc_id)
+			     __field(u8, gt_id)
 			     ),
 
 		    TP_fast_assign(
@@ -291,9 +292,11 @@ DECLARE_EVENT_CLASS(xe_sched_msg,
 			   __entry->opcode = msg->opcode;
 			   __entry->guc_id =
 			   ((struct xe_exec_queue *)msg->private_data)->guc->id;
+			   __entry->gt_id =
+			   ((struct xe_exec_queue *)msg->private_data)->gt->info.id;
 			   ),
 
-		    TP_printk("dev=%s, guc_id=%d, opcode=%u", __get_str(dev), __entry->guc_id,
+		    TP_printk("dev=%s, gt=%u guc_id=%d, opcode=%u", __get_str(dev), __entry->gt_id, __entry->guc_id,
 			      __entry->opcode)
 );
 
-- 
2.47.0


             reply	other threads:[~2024-11-22 16:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 16:19 Matthew Auld [this message]
2024-11-22 16:19 ` [PATCH 2/3] drm/xe/guc_submit: fix race around pending_disable Matthew Auld
2024-11-23  0:23   ` Matthew Brost
2024-11-22 16:19 ` [PATCH 3/3] drm/xe/guc_submit: fix race around suspend_pending Matthew Auld
2024-11-25 23:42   ` Matthew Brost
2024-11-22 16:27 ` ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe/trace: improve xe_sched_msg trace Patchwork
2024-11-22 16:28 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-22 16:29 ` ✓ CI.KUnit: success " Patchwork
2024-11-22 16:47 ` ✓ CI.Build: " Patchwork
2024-11-22 16:49 ` ✓ CI.Hooks: " Patchwork
2024-11-22 16:51 ` ✓ CI.checksparse: " Patchwork
2024-11-22 17:15 ` ✓ Xe.CI.BAT: " Patchwork
2024-11-22 20:46 ` [PATCH 1/3] " Lucas De Marchi
2024-11-23 18:56 ` ✗ Xe.CI.Full: failure for series starting with [1/3] " Patchwork

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=20241122161914.321263-4-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox