From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org, kernel-dev@igalia.com,
Tejas Upadhyay <tejas.upadhyay@intel.com>,
Aradhya Bhatia <aradhya.bhatia@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH v4 1/9] drm/xe/xelpg: Move Wa_14016712196 to the invalidate path
Date: Tue, 1 Apr 2025 09:46:34 +0100 [thread overview]
Message-ID: <c81f601a-1797-4dc0-9208-b1454afa7690@igalia.com> (raw)
In-Reply-To: <Z-rk8xcPursz8lUu@intel.com>
On 31/03/2025 19:54, Rodrigo Vivi wrote:
> On Fri, Mar 28, 2025 at 04:35:28PM +0000, Tvrtko Ursulin wrote:
>> According to i915 Wa_14016712196 needs to be emmited before a
>> pipe control which contains a post sync operation.
>>
>> Therefore move it from flush (no post sync) to invalidate (post sync).
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
>> Fixes: 8c5fe7d88bc1 ("drm/xe: Add Wa_16021333562 and Wa_14016712196")
>> Cc: Tejas Upadhyay <tejas.upadhyay@intel.com>
>> Cc: Aradhya Bhatia <aradhya.bhatia@intel.com>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> ---
>> Please double check.
>
> It looks like both options are possible.
>
> We either insert a PIPE_CONTROL with "**Depth Flush** " post any state that
> will send an implicit depth flush and prior to any PIPE_CONTROL. This
> PIPE_CONTROL is not required if 3DPRIMITIVE, 3DMESH or PIPE_CONTROL that
> doesn't require end of the pipe drain is programmed prior to a PIPE_CONTROL
> that requires end of the pipe drain and hits this issue.
>
> or
>
> We insert a this pipe_control prior to PIPE_CONTROL which will hit the issue. For
> timestamp, this could be a replicated pipe_control as it will write the
> correct value the 2nd time. For post sync with write immediate, SW would have
> to allocate a dummy address.
>
> So, is changing the order really helping your case or needed for your case?
No, I don't have access to Meteorlake so I was just comparing all the
differences between i915 and xe in this area. Given Juha-Pekka reported
the previous version of this series did not work there. I suspect that
problem was I simply miscounted MAX_JOB_SIZE_DW. That should be fixed in
this v4. So yeah, if you say this patch is wrong or not needed I will
drop it.
Regards,
Tvrtko
>> ---
>> drivers/gpu/drm/xe/xe_ring_ops.c | 16 +++++++++-------
>> 1 file changed, 9 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_ring_ops.c b/drivers/gpu/drm/xe/xe_ring_ops.c
>> index 917fc16de866..88591b7a7715 100644
>> --- a/drivers/gpu/drm/xe/xe_ring_ops.c
>> +++ b/drivers/gpu/drm/xe/xe_ring_ops.c
>> @@ -134,8 +134,9 @@ emit_pipe_control(u32 *dw, int i, u32 bit_group_0, u32 bit_group_1, u32 offset,
>> return i;
>> }
>>
>> -static int emit_pipe_invalidate(u32 mask_flags, bool invalidate_tlb, u32 *dw,
>> - int i)
>> +static int
>> +emit_pipe_invalidate(struct xe_gt *gt, u32 mask_flags, bool invalidate_tlb,
>> + u32 *dw, int i)
>> {
>> u32 flags = PIPE_CONTROL_CS_STALL |
>> PIPE_CONTROL_COMMAND_CACHE_INVALIDATE |
>> @@ -152,6 +153,10 @@ static int emit_pipe_invalidate(u32 mask_flags, bool invalidate_tlb, u32 *dw,
>>
>> flags &= ~mask_flags;
>>
>> + if (XE_WA(gt, 14016712196))
>> + i = emit_pipe_control(dw, i, 0, PIPE_CONTROL_DEPTH_CACHE_FLUSH,
>> + LRC_PPHWSP_FLUSH_INVAL_SCRATCH_ADDR, 0);
>> +
>> return emit_pipe_control(dw, i, 0, flags, LRC_PPHWSP_FLUSH_INVAL_SCRATCH_ADDR, 0);
>> }
>>
>> @@ -173,10 +178,6 @@ static int emit_render_cache_flush(struct xe_sched_job *job, u32 *dw, int i)
>> bool lacks_render = !(gt->info.engine_mask & XE_HW_ENGINE_RCS_MASK);
>> u32 flags;
>>
>> - if (XE_WA(gt, 14016712196))
>> - i = emit_pipe_control(dw, i, 0, PIPE_CONTROL_DEPTH_CACHE_FLUSH,
>> - LRC_PPHWSP_FLUSH_INVAL_SCRATCH_ADDR, 0);
>> -
>> flags = (PIPE_CONTROL_CS_STALL |
>> PIPE_CONTROL_TILE_CACHE_FLUSH |
>> PIPE_CONTROL_RENDER_TARGET_CACHE_FLUSH |
>> @@ -361,7 +362,8 @@ static void __emit_job_gen12_render_compute(struct xe_sched_job *job,
>> mask_flags = PIPE_CONTROL_3D_ENGINE_FLAGS;
>>
>> /* See __xe_pt_bind_vma() for a discussion on TLB invalidations. */
>> - i = emit_pipe_invalidate(mask_flags, job->ring_ops_flush_tlb, dw, i);
>> + i = emit_pipe_invalidate(gt, mask_flags, job->ring_ops_flush_tlb, dw,
>> + i);
>>
>> /* hsdes: 1809175790 */
>> if (has_aux_ccs(xe))
>> --
>> 2.48.0
>>
next prev parent reply other threads:[~2025-04-01 8:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 16:35 [PATCH v4 0/9] AuxCCS handling and render compression modifiers Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 1/9] drm/xe/xelpg: Move Wa_14016712196 to the invalidate path Tvrtko Ursulin
2025-03-31 18:54 ` Rodrigo Vivi
2025-04-01 8:46 ` Tvrtko Ursulin [this message]
2025-03-28 16:35 ` [PATCH v4 2/9] drm/xe: Add ring buffer handling for AuxCCS Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 3/9] drm/xe: Use fb cached min alignment Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 4/9] drm/xe: Reduce DPT table alignment as in i915 Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 5/9] drm/xe: Flush GGTT writes after populating DPT Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 6/9] drm/xe: Handle DPT in system memory Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 7/9] drm/xe: Force flush system memory AuxCCS framebuffers before scan out Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 8/9] drm/xe/display: Add support for AuxCCS Tvrtko Ursulin
2025-03-28 16:35 ` [PATCH v4 9/9] drm/i915/display: Expose AuxCCS frame buffer modifiers for Xe Tvrtko Ursulin
2025-03-31 18:55 ` Rodrigo Vivi
2025-03-28 17:33 ` ✓ CI.Patch_applied: success for AuxCCS handling and render compression modifiers (rev4) Patchwork
2025-03-28 17:33 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-28 17:34 ` ✓ CI.KUnit: success " Patchwork
2025-03-28 17:51 ` ✓ CI.Build: " Patchwork
2025-03-28 17:53 ` ✓ CI.Hooks: " Patchwork
2025-03-28 17:55 ` ✓ CI.checksparse: " Patchwork
2025-03-28 18:35 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-29 7:44 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-02 11:42 ` [PATCH v4 0/9] AuxCCS handling and render compression modifiers Juha-Pekka Heikkilä
2025-04-02 15:30 ` Tvrtko Ursulin
2025-04-03 10:16 ` Tvrtko Ursulin
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=c81f601a-1797-4dc0-9208-b1454afa7690@igalia.com \
--to=tvrtko.ursulin@igalia.com \
--cc=aradhya.bhatia@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tejas.upadhyay@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