Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Graunke <kenneth@whitecape.org>
To: intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 0/7] Fix ctx workarounds for non-masked regs
Date: Fri, 30 Jun 2023 17:41:21 -0700	[thread overview]
Message-ID: <4528180.ln3aigfREe@mizzik> (raw)
In-Reply-To: <20230630203509.1635216-1-lucas.demarchi@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Friday, June 30, 2023 1:35:02 PM PDT Lucas De Marchi wrote:
> v3 of https://patchwork.freedesktop.org/series/119766/
> 
> Changes from v2:
> 
> 	- Do not rmw if (clr | set) covers all bits
> 	- Add patch to make sure the set bits are also checked on
> 	  wa_*_clr_set() when clr is not a superset.
> 
> Tested on DG2 with intel_reg reading 0xb158 with a busy render engine.
> Now it's not losing the upper bit anymore.
> 
> Lucas De Marchi (7):
>   drm/i915/gt: Move wal_get_fw_for_rmw()
>   drm/i915/gt: Clear all bits from GEN12_FF_MODE2
>   drm/i915/gt: Fix context workarounds with non-masked regs
>   drm/i915/gt: Drop read from GEN8_L3CNTLREG in ICL workaround
>   drm/i915/gt: Enable read back on XEHP_FF_MODE2
>   drm/i915/gt: Remove bogus comment on IVB_FBC_RT_BASE_UPPER
>   drm/i915/gt: Also check set bits in clr_set()
> 
>  drivers/gpu/drm/i915/gt/intel_workarounds.c | 129 ++++++++++----------
>  1 file changed, 66 insertions(+), 63 deletions(-)

Whole series is now:

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>

Thanks a lot for fixing this, Lucas!

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-07-01  0:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 20:35 [Intel-gfx] [PATCH v3 0/7] Fix ctx workarounds for non-masked regs Lucas De Marchi
2023-06-30 20:35 ` [Intel-gfx] [PATCH v3 1/7] drm/i915/gt: Move wal_get_fw_for_rmw() Lucas De Marchi
2023-06-30 20:35 ` [Intel-gfx] [PATCH v3 2/7] drm/i915/gt: Clear all bits from GEN12_FF_MODE2 Lucas De Marchi
2023-06-30 20:35 ` [Intel-gfx] [PATCH v3 3/7] drm/i915/gt: Fix context workarounds with non-masked regs Lucas De Marchi
2023-06-30 20:35 ` [Intel-gfx] [PATCH v3 4/7] drm/i915/gt: Drop read from GEN8_L3CNTLREG in ICL workaround Lucas De Marchi
2023-06-30 20:35 ` [Intel-gfx] [PATCH v3 5/7] drm/i915/gt: Enable read back on XEHP_FF_MODE2 Lucas De Marchi
2023-06-30 20:35 ` [Intel-gfx] [PATCH v3 6/7] drm/i915/gt: Remove bogus comment on IVB_FBC_RT_BASE_UPPER Lucas De Marchi
2023-06-30 20:35 ` [Intel-gfx] [PATCH v3 7/7] drm/i915/gt: Also check set bits in clr_set() Lucas De Marchi
2023-06-30 21:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix ctx workarounds for non-masked regs (rev3) Patchwork
2023-06-30 21:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-01  0:41 ` Kenneth Graunke [this message]
2023-07-03 18:41   ` [Intel-gfx] [PATCH v3 0/7] Fix ctx workarounds for non-masked regs Lucas De Marchi
2023-07-01 12:03 ` [Intel-gfx] ✓ Fi.CI.IGT: success for Fix ctx workarounds for non-masked regs (rev3) 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=4528180.ln3aigfREe@mizzik \
    --to=kenneth@whitecape.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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