All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Cc: intel-gfx@lists.freedesktop.org, andi.shyti@linux.intel.com,
	vidya.srinivas@intel.com, matthew.d.roper@intel.com
Subject: Re: [RFC PATCH] Revert "drm/i915: Disable compression tricks on JSL"
Date: Thu, 6 Mar 2025 14:52:24 +0200	[thread overview]
Message-ID: <Z8maiLd63cK-PUnU@intel.com> (raw)
In-Reply-To: <D88HRP898QST.23MJT5TUM1HFR@intel.com>

On Wed, Mar 05, 2025 at 05:00:26PM +0000, Sebastian Brzezinka wrote:
> Hi Ville
> 
> On Wed Mar 5, 2025 at 3:26 PM UTC, Ville Syrjälä wrote:
> > On Wed, Mar 05, 2025 at 02:49:46PM +0000, Sebastian Brzezinka wrote:
> >> This reverts commit 0ddae025ab6cefa9aba757da3cd1d27908d70b0e.
> >> 
> >> According to bspec 14181, CACHE_MODE_0 is a register that's under userspace
> >> control, and DISABLE_REPACKING_FOR_COMPRESSION workaround should be already
> >> in all recent Mesa releases. So, there is no need to include it in kernel.
> >
> > igt doesn't have it.
> >
> >> 
> >> Also, this workaround·sporadically fails to load:
> >> ```
> >> ERROR GT0: engine workaround lost on application! (reg[7000]=0x0,
> >> relevant bits were 0x0 vs expected 0x8000)
> >> ```
> >
> > If it somehow fails to load from the kernel why would it
> > work from userspace?
> >
> > Hmm, apparently CACHE_MODE_0 needs the mcr steering stuff.
> > Does that fix the verification fail?
> 
> Thanks for sugestion. Right now I think that I try to move this wa to
> icl_ctx_workarounds_init as both Mat and Chriss notice that register
> is a part of the context. 

Hmm, didn't realize there was a separate list for that. It looks to
me like there are a bunch of context saved registers handled in
the enging_ctx() stuff currently. I think someone needs to go through
all this stuff and relocate all the registers to their correct spots.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2025-03-06 12:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 14:49 [RFC PATCH] Revert "drm/i915: Disable compression tricks on JSL" Sebastian Brzezinka
2025-03-05 15:03 ` Sebastian Brzezinka
2025-03-05 15:26 ` Ville Syrjälä
2025-03-05 17:00   ` Sebastian Brzezinka
2025-03-06 12:52     ` Ville Syrjälä [this message]
2025-03-05 19:16 ` ✓ i915.CI.BAT: success for " Patchwork
2025-03-05 21:41 ` ✗ i915.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=Z8maiLd63cK-PUnU@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=sebastian.brzezinka@intel.com \
    --cc=vidya.srinivas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.