From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Brost, Matthew" <matthew.brost@intel.com>
Cc: "Vivekanandan,
Balasubramani" <balasubramani.vivekanandan@intel.com>,
"Souza, Jose" <jose.souza@intel.com>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
"Mrozek, Michal" <michal.mrozek@intel.com>
Subject: Re: [PATCH] drm/xe: Mark ComputeCS read mode as UC on iGPU
Date: Tue, 14 Jan 2025 00:11:16 +0000 [thread overview]
Message-ID: <8b439e8476790b71efee6d883aa4050220bf56ba.camel@intel.com> (raw)
In-Reply-To: <e55de9e1a876069e2552e1d07e2d37b0b9acd0fd.camel@intel.com>
On Mon, 2025-01-13 at 23:57 +0000, Summers, Stuart wrote:
> On Thu, 2024-12-12 at 15:46 -0800, Matthew Brost wrote:
> > RING_CMD_CCTL read index should be UC on iGPU parts due to L3
> > caching
> > structure. Having this as WB blocks ULLS from being enabled. Change
> > to
> > UC to unblock ULLS on iGPU.
> >
> > Cc: Balasubramani Vivekanandan
> > <balasubramani.vivekanandan@intel.com>
> > Cc: Michal Mrozek <michal.mrozek@intel.com>
> > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Cc: José Roberto de Souza <jose.souza@intel.com>
> > Cc: stable@vger.kernel.org
> > Fixes: 328e089bfb37 ("drm/xe: Leverage ComputeCS read L3 caching")
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_hw_engine.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c
> > b/drivers/gpu/drm/xe/xe_hw_engine.c
> > index b19366744148..cc258b2a77c9 100644
> > --- a/drivers/gpu/drm/xe/xe_hw_engine.c
> > +++ b/drivers/gpu/drm/xe/xe_hw_engine.c
> > @@ -417,9 +417,14 @@ hw_engine_setup_default_state(struct
> > xe_hw_engine *hwe)
> > * entry is recommended by the spec in certain
> > circumstances
> > on
> > * specific platforms.
> > * Bspec: 72161
> > + *
> > + * XXX: According to internal communications bspec is wrong
> > and
>
> Can you remove this reference to "internal communications"? It looks
> like from the latest in bspec this is pretty clear.
>
> I do see one test regressing on LNL, can you double check that this
> isn't related to the caching change before we merge this?
>
> Otherwise lgtm
Reviewed-by: Stuart Summers <stuart.summers@intel.com>
Before merging, can you get a CI re-run of this since it's now been a
month or so and we have that LNL failure? It doesn't seem related here,
but I don't see anything in ci-buglog right now that looks specifically
like that signature.
Thanks,
Stuart
>
> Thanks,
> Stuart
>
> > + * RING_CMD_CCTL read index should be UC on iGPU parts due
> > to
> > L3 caching
> > + * structure. Having this as WB blocks ULLS from being
> > enabled. Add
> > + * bspec link or delete this comment once bspec is updated.
> > */
> > const u8 mocs_write_idx = gt->mocs.uc_index;
> > - const u8 mocs_read_idx = hwe->class ==
> > XE_ENGINE_CLASS_COMPUTE &&
> > + const u8 mocs_read_idx = hwe->class ==
> > XE_ENGINE_CLASS_COMPUTE && IS_DGFX(xe) &&
> > (GRAPHICS_VER(xe) >= 20 || xe-
> > > info.platform == XE_PVC) ?
> > gt->mocs.wb_index : gt-
> > > mocs.uc_index;
> > u32 ring_cmd_cctl_val =
> > REG_FIELD_PREP(CMD_CCTL_WRITE_OVERRIDE_MASK, mocs_write_idx) |
>
prev parent reply other threads:[~2025-01-14 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 23:46 [PATCH] drm/xe: Mark ComputeCS read mode as UC on iGPU Matthew Brost
2024-12-13 0:20 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-13 0:20 ` ✓ CI.checkpatch: " Patchwork
2024-12-13 0:21 ` ✓ CI.KUnit: " Patchwork
2024-12-13 0:39 ` ✓ CI.Build: " Patchwork
2024-12-13 0:42 ` ✓ CI.Hooks: " Patchwork
2024-12-13 0:43 ` ✓ CI.checksparse: " Patchwork
2024-12-13 1:14 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-13 4:13 ` [PATCH] " Mrozek, Michal
2024-12-13 8:39 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-01-13 23:50 ` Summers, Stuart
2025-01-13 23:57 ` [PATCH] " Summers, Stuart
2025-01-14 0:11 ` Summers, Stuart [this message]
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=8b439e8476790b71efee6d883aa4050220bf56ba.camel@intel.com \
--to=stuart.summers@intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.mrozek@intel.com \
--cc=paulo.r.zanoni@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