From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com
Subject: [RFC PATCH 1/8] drm/xe: Add xe_hw_engine_write_ring_tail
Date: Sun, 11 Aug 2024 19:47:10 -0700 [thread overview]
Message-ID: <20240812024717.3584636-2-matthew.brost@intel.com> (raw)
In-Reply-To: <20240812024717.3584636-1-matthew.brost@intel.com>
ULLS for migration jobs need to directly set hw engine ring tail.
Signed-off-by: Matthew Brost <matthew.brost@intel.com
---
drivers/gpu/drm/xe/xe_hw_engine.c | 10 ++++++++++
drivers/gpu/drm/xe/xe_hw_engine.h | 1 +
2 files changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c b/drivers/gpu/drm/xe/xe_hw_engine.c
index 402dfa748e16..ee006b393e2f 100644
--- a/drivers/gpu/drm/xe/xe_hw_engine.c
+++ b/drivers/gpu/drm/xe/xe_hw_engine.c
@@ -298,6 +298,16 @@ void xe_hw_engine_mmio_write32(struct xe_hw_engine *hwe,
xe_mmio_write32(hwe->gt, reg, val);
}
+/**
+ * xe_hw_engine_write_ring_tail() - Write ring tail
+ * @hwe: engine
+ * @val: desired 32-bit value to write
+ */
+void xe_hw_engine_write_ring_tail(struct xe_hw_engine *hwe, u32 val)
+{
+ xe_hw_engine_mmio_write32(hwe, RING_TAIL(0), val);
+}
+
/**
* xe_hw_engine_mmio_read32() - Read engine register
* @hwe: engine
diff --git a/drivers/gpu/drm/xe/xe_hw_engine.h b/drivers/gpu/drm/xe/xe_hw_engine.h
index 022819a4a8eb..076230b158b3 100644
--- a/drivers/gpu/drm/xe/xe_hw_engine.h
+++ b/drivers/gpu/drm/xe/xe_hw_engine.h
@@ -80,5 +80,6 @@ enum xe_force_wake_domains xe_hw_engine_to_fw_domain(struct xe_hw_engine *hwe);
void xe_hw_engine_mmio_write32(struct xe_hw_engine *hwe, struct xe_reg reg, u32 val);
u32 xe_hw_engine_mmio_read32(struct xe_hw_engine *hwe, struct xe_reg reg);
+void xe_hw_engine_write_ring_tail(struct xe_hw_engine *hwe, u32 val);
#endif
--
2.34.1
next prev parent reply other threads:[~2024-08-12 2:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 2:47 [RFC PATCH 0/8] ULLS for kernel submission of migration jobs Matthew Brost
2024-08-12 2:47 ` Matthew Brost [this message]
2024-08-12 2:47 ` [RFC PATCH 2/8] drm/xe: Add ULLS support to LRC Matthew Brost
2024-08-12 2:47 ` [RFC PATCH 3/8] drm/xe: Add ULLS flags for jobs Matthew Brost
2024-08-12 2:47 ` [RFC PATCH 4/8] drm/xe: Add ULLS migration job support to migration layer Matthew Brost
2024-08-12 2:47 ` [RFC PATCH 5/8] drm/xe: Add MI_SEMAPHORE_WAIT instruction defs Matthew Brost
2024-08-12 2:47 ` [RFC PATCH 6/8] drm/xe: Add ULLS migration job support to ring ops Matthew Brost
2024-08-12 2:47 ` [RFC PATCH 7/8] drm/xe: Add ULLS migration job support to GuC submission Matthew Brost
2024-08-12 2:47 ` [RFC PATCH 8/8] drm/xe: Enable ULLS migration jobs when opening LR VM Matthew Brost
2024-08-12 2:51 ` ✓ CI.Patch_applied: success for ULLS for kernel submission of migration jobs Patchwork
2024-08-12 2:52 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-12 2:53 ` ✓ CI.KUnit: success " Patchwork
2024-08-12 3:05 ` ✓ CI.Build: " Patchwork
2024-08-12 3:07 ` ✓ CI.Hooks: " Patchwork
2024-08-12 3:08 ` ✓ CI.checksparse: " Patchwork
2024-08-12 3:28 ` ✓ CI.BAT: " Patchwork
2024-08-12 4:31 ` ✗ CI.FULL: failure " Patchwork
2024-08-12 8:53 ` [RFC PATCH 0/8] " Thomas Hellström
2024-08-12 17:26 ` Matthew Brost
2024-09-16 13:55 ` Matthew Brost
2024-09-17 6:59 ` Thomas Hellström
2024-09-17 14:39 ` Matthew Brost
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=20240812024717.3584636-2-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.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