Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [PATCH v17 5/7] drm/xe/guc: Move xe_lrc_snapshot to header file
Date: Tue, 27 Aug 2024 14:47:24 -0700	[thread overview]
Message-ID: <20240827214726.1183935-6-zhanjun.dong@intel.com> (raw)
In-Reply-To: <20240827214726.1183935-1-zhanjun.dong@intel.com>

Move xe_lrc_snapshot structure define to header file, GuC capture feature
need to access structure fields.

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
---
 drivers/gpu/drm/xe/xe_lrc.c       | 18 ------------------
 drivers/gpu/drm/xe/xe_lrc_types.h | 18 +++++++++++++++++-
 2 files changed, 17 insertions(+), 19 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_lrc.c b/drivers/gpu/drm/xe/xe_lrc.c
index aec7db39c061..52f8d202e262 100644
--- a/drivers/gpu/drm/xe/xe_lrc.c
+++ b/drivers/gpu/drm/xe/xe_lrc.c
@@ -38,24 +38,6 @@
 
 #define LRC_INDIRECT_RING_STATE_SIZE		SZ_4K
 
-struct xe_lrc_snapshot {
-	struct xe_bo *lrc_bo;
-	void *lrc_snapshot;
-	unsigned long lrc_size, lrc_offset;
-
-	u32 context_desc;
-	u32 indirect_context_desc;
-	u32 head;
-	struct {
-		u32 internal;
-		u32 memory;
-	} tail;
-	u32 start_seqno;
-	u32 seqno;
-	u32 ctx_timestamp;
-	u32 ctx_job_timestamp;
-};
-
 static struct xe_device *
 lrc_to_xe(struct xe_lrc *lrc)
 {
diff --git a/drivers/gpu/drm/xe/xe_lrc_types.h b/drivers/gpu/drm/xe/xe_lrc_types.h
index 71ecb453f811..011d4607e585 100644
--- a/drivers/gpu/drm/xe/xe_lrc_types.h
+++ b/drivers/gpu/drm/xe/xe_lrc_types.h
@@ -55,6 +55,22 @@ struct xe_lrc {
 	u32 ctx_timestamp;
 };
 
-struct xe_lrc_snapshot;
+struct xe_lrc_snapshot {
+	struct xe_bo *lrc_bo;
+	void *lrc_snapshot;
+	unsigned long lrc_size, lrc_offset;
+
+	u32 context_desc;
+	u32 indirect_context_desc;
+	u32 head;
+	struct {
+		u32 internal;
+		u32 memory;
+	} tail;
+	u32 start_seqno;
+	u32 seqno;
+	u32 ctx_timestamp;
+	u32 ctx_job_timestamp;
+};
 
 #endif
-- 
2.34.1


  parent reply	other threads:[~2024-08-27 21:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 21:47 [PATCH v17 0/7] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-08-27 21:47 ` [PATCH v17 1/7] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-08-27 23:05   ` Teres Alexis, Alan Previn
2024-08-27 21:47 ` [PATCH v17 2/7] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-08-28 22:12   ` Teres Alexis, Alan Previn
2024-08-27 21:47 ` [PATCH v17 3/7] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-08-27 21:47 ` [PATCH v17 4/7] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-08-28  0:22   ` Teres Alexis, Alan Previn
2024-08-27 21:47 ` Zhanjun Dong [this message]
2024-08-27 22:32   ` [PATCH v17 5/7] drm/xe/guc: Move xe_lrc_snapshot to header file Teres Alexis, Alan Previn
2024-08-27 21:47 ` [PATCH v17 6/7] drm/xe/guc: Add dss conversion from group/instance ID Zhanjun Dong
2024-08-27 23:15   ` Teres Alexis, Alan Previn
2024-08-27 21:47 ` [PATCH v17 7/7] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-08-29  4:26   ` Teres Alexis, Alan Previn
2024-09-06 18:11     ` Dong, Zhanjun
2024-08-27 21:53 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev17) Patchwork
2024-08-27 21:53 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-27 21:54 ` ✓ CI.KUnit: success " Patchwork
2024-08-27 22:09 ` ✓ CI.Build: " Patchwork
2024-08-27 22:12 ` ✓ CI.Hooks: " Patchwork
2024-08-27 22:14 ` ✓ CI.checksparse: " Patchwork
2024-08-27 22:35 ` ✓ CI.BAT: " Patchwork
2024-08-28  7:41 ` ✗ 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=20240827214726.1183935-6-zhanjun.dong@intel.com \
    --to=zhanjun.dong@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