From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/xe: Move LRC_ENGINE_ID_PPHWSP_OFFSET outside of parallel offset
Date: Fri, 13 Jun 2025 09:38:12 -0700 [thread overview]
Message-ID: <aExT9LQ-OsDMMLen@unerlige-desk.amr.corp.intel.com> (raw)
In-Reply-To: <20250612172850.4170428-1-matthew.brost@intel.com>
On Thu, Jun 12, 2025 at 10:28:50AM -0700, Matthew Brost wrote:
>The parallel scratch layout spans 2k and LRC_ENGINE_ID_PPHWSP_OFFSET
>lands within than space. This happens to be ok as the offset lands in
>reserved part of guc_sched_wq_desc, but for future safety move
>LRC_ENGINE_ID_PPHWSP_OFFSET to the unused offset of 1024 below parallel
>scratch layout.
Oh, didn't know that. If you could add that info in a comment above
LRC_PARALLEL_PPHWSP_OFFSET, it would help anyone adding new stuff in
future. Ideally we should update the bspec at some point here - 77575
and guide everyone to look there for overlaps.
Change LGTM from utilization perspective, so with or without the above,
Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Thanks,
Umesh
>
>Signed-off-by: Matthew Brost <matthew.brost@intel.com>
>---
> drivers/gpu/drm/xe/xe_lrc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/gpu/drm/xe/xe_lrc.c b/drivers/gpu/drm/xe/xe_lrc.c
>index 529c6a972a55..6fb2a2ca4e78 100644
>--- a/drivers/gpu/drm/xe/xe_lrc.c
>+++ b/drivers/gpu/drm/xe/xe_lrc.c
>@@ -654,8 +654,8 @@ u32 xe_lrc_pphwsp_offset(struct xe_lrc *lrc)
> #define LRC_SEQNO_PPHWSP_OFFSET 512
> #define LRC_START_SEQNO_PPHWSP_OFFSET (LRC_SEQNO_PPHWSP_OFFSET + 8)
> #define LRC_CTX_JOB_TIMESTAMP_OFFSET (LRC_START_SEQNO_PPHWSP_OFFSET + 8)
>+#define LRC_ENGINE_ID_PPHWSP_OFFSET 1024
> #define LRC_PARALLEL_PPHWSP_OFFSET 2048
>-#define LRC_ENGINE_ID_PPHWSP_OFFSET 2096
>
> u32 xe_lrc_regs_offset(struct xe_lrc *lrc)
> {
>--
>2.34.1
>
next prev parent reply other threads:[~2025-06-13 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 17:28 [PATCH] drm/xe: Move LRC_ENGINE_ID_PPHWSP_OFFSET outside of parallel offset Matthew Brost
2025-06-12 20:34 ` ✓ CI.KUnit: success for " Patchwork
2025-06-13 12:42 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-13 16:38 ` Umesh Nerlige Ramappa [this message]
2025-06-13 20:12 ` [PATCH] " Matthew Brost
2025-06-13 22:39 ` ✓ CI.KUnit: success for drm/xe: Move LRC_ENGINE_ID_PPHWSP_OFFSET outside of parallel offset (rev2) Patchwork
2025-06-13 23:16 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-15 22:53 ` ✓ Xe.CI.Full: " 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=aExT9LQ-OsDMMLen@unerlige-desk.amr.corp.intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--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