Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH v3 4/6] drm/xe: Add ctx timestamp to LRC snapshot
Date: Fri,  7 Jun 2024 17:21:01 -0700	[thread overview]
Message-ID: <20240608002103.2371696-5-matthew.brost@intel.com> (raw)
In-Reply-To: <20240608002103.2371696-1-matthew.brost@intel.com>

The ctx timestamp is useful information, add to LRC snapshot.

v2:
  - s/ctx_timestamp_job/ctx_job_timestamp

Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_lrc.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/gpu/drm/xe/xe_lrc.c b/drivers/gpu/drm/xe/xe_lrc.c
index 0fef354c6489..f3d77aa1750d 100644
--- a/drivers/gpu/drm/xe/xe_lrc.c
+++ b/drivers/gpu/drm/xe/xe_lrc.c
@@ -49,6 +49,8 @@ struct xe_lrc_snapshot {
 	} tail;
 	u32 start_seqno;
 	u32 seqno;
+	u32 ctx_timestamp;
+	u32 ctx_job_timestamp;
 };
 
 static struct xe_device *
@@ -1642,6 +1644,8 @@ struct xe_lrc_snapshot *xe_lrc_snapshot_capture(struct xe_lrc *lrc)
 	snapshot->lrc_offset = xe_lrc_pphwsp_offset(lrc);
 	snapshot->lrc_size = lrc->bo->size - snapshot->lrc_offset;
 	snapshot->lrc_snapshot = NULL;
+	snapshot->ctx_timestamp = xe_lrc_ctx_timestamp(lrc);
+	snapshot->ctx_job_timestamp = xe_lrc_ctx_job_timestamp(lrc);
 	return snapshot;
 }
 
@@ -1690,6 +1694,8 @@ void xe_lrc_snapshot_print(struct xe_lrc_snapshot *snapshot, struct drm_printer
 		   snapshot->tail.internal, snapshot->tail.memory);
 	drm_printf(p, "\tStart seqno: (memory) %d\n", snapshot->start_seqno);
 	drm_printf(p, "\tSeqno: (memory) %d\n", snapshot->seqno);
+	drm_printf(p, "\tTimestamp: 0x%08x\n", snapshot->ctx_timestamp);
+	drm_printf(p, "\tJob Timestamp: 0x%08x\n", snapshot->ctx_job_timestamp);
 
 	if (!snapshot->lrc_snapshot)
 		return;
-- 
2.34.1


  parent reply	other threads:[~2024-06-08  0:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-08  0:20 [PATCH v3 0/6] Only timeout jobs if they run longer than timeout period Matthew Brost
2024-06-08  0:20 ` [PATCH v3 1/6] drm/xe: Add LRC ctx timestamp support functions Matthew Brost
2024-06-10 13:49   ` Lucas De Marchi
2024-06-10 14:10     ` Matthew Brost
2024-06-10 17:42       ` Lucas De Marchi
2024-06-08  0:20 ` [PATCH v3 2/6] drm/xe: Add MI_COPY_MEM_MEM GPU instruction definitions Matthew Brost
2024-06-08  0:21 ` [PATCH v3 3/6] drm/xe: Emit ctx timestamp copy in ring ops Matthew Brost
2024-06-08  0:21 ` Matthew Brost [this message]
2024-06-08  0:21 ` [PATCH v3 5/6] drm/xe: Add xe_gt_clock_interval_to_ms helper Matthew Brost
2024-06-08  0:21 ` [PATCH v3 6/6] drm/xe: Sample ctx timestamp to determine if jobs have timed out Matthew Brost
2024-06-08  2:13   ` John Harrison
2024-06-08  2:29     ` Matthew Brost
2024-06-08  0:25 ` ✓ CI.Patch_applied: success for Only timeout jobs if they run longer than timeout period Patchwork
2024-06-08  0:25 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-08  0:26 ` ✓ CI.KUnit: success " Patchwork
2024-06-08  0:37 ` ✓ CI.Build: " Patchwork
2024-06-08  0:39 ` ✗ CI.Hooks: failure " Patchwork
2024-06-08  0:41 ` ✓ CI.checksparse: success " Patchwork
2024-06-08  1:27 ` ✓ CI.BAT: " Patchwork
2024-06-08 16:55 ` ✗ CI.FULL: failure " 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=20240608002103.2371696-5-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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