From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: intel-xe@lists.freedesktop.org
Subject: [CI 00/13] auxccs late flush
Date: Tue, 19 Aug 2025 09:55:21 +0100 [thread overview]
Message-ID: <20250819085537.97902-1-tvrtko.ursulin@igalia.com> (raw)
i915 sets up the async flush which triggers when the atomic commit waits
on the fences. That is later than straight after the pin so lets try
that since we are desperate...
Tvrtko Ursulin (13):
drm/xe/xelpg: Flush CCS when flushing caches
drm/xe/xelp: Quiesce memory traffic before invalidating auxccs
drm/xe/xelp: Support auxccs invalidation on blitter
drm/xe/xelp: Use MI_FLUSH_DW_CCS on auxccs platforms
drm/xe/xelp: Wait for AuxCCS invalidation to complete
drm/xe: Export xe_emit_aux_table_inv
drm/xe/xelp: Add AuxCCS invalidation to the indirect context
workarounds
drm/xe: Flush GGTT writes after populating DPT
drm/xe: Handle DPT in system memory
drm/xe/display: Add support for AuxCCS
drm/xe: Force flush system memory AuxCCS data before scan out
late flush
drm/i915/display: Expose AuxCCS frame buffer modifiers for Xe
drivers/gpu/drm/i915/display/intel_display.c | 15 +-
.../drm/i915/display/skl_universal_plane.c | 6 -
drivers/gpu/drm/i915/gem/i915_gem_object.h | 5 +
.../compat-i915-headers/gem/i915_gem_object.h | 2 +
drivers/gpu/drm/xe/display/xe_fb_pin.c | 183 +++++++++++++++---
.../gpu/drm/xe/instructions/xe_gpu_commands.h | 1 +
.../gpu/drm/xe/instructions/xe_mi_commands.h | 6 +
drivers/gpu/drm/xe/regs/xe_gt_regs.h | 1 +
drivers/gpu/drm/xe/xe_bo_types.h | 14 +-
drivers/gpu/drm/xe/xe_lrc.c | 47 +++++
drivers/gpu/drm/xe/xe_ring_ops.c | 161 +++++++--------
drivers/gpu/drm/xe/xe_ring_ops.h | 3 +
drivers/gpu/drm/xe/xe_ring_ops_types.h | 2 +-
13 files changed, 328 insertions(+), 118 deletions(-)
--
2.48.0
next reply other threads:[~2025-08-19 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 8:55 Tvrtko Ursulin [this message]
2025-08-19 8:55 ` [CI 01/13] drm/xe/xelpg: Flush CCS when flushing caches Tvrtko Ursulin
2025-08-19 8:55 ` [CI 02/13] drm/xe/xelp: Quiesce memory traffic before invalidating auxccs Tvrtko Ursulin
2025-08-19 8:55 ` [CI 03/13] drm/xe/xelp: Support auxccs invalidation on blitter Tvrtko Ursulin
2025-08-19 8:55 ` [CI 04/13] drm/xe/xelp: Use MI_FLUSH_DW_CCS on auxccs platforms Tvrtko Ursulin
2025-08-19 8:55 ` [CI 05/13] drm/xe/xelp: Wait for AuxCCS invalidation to complete Tvrtko Ursulin
2025-08-19 8:55 ` [CI 06/13] drm/xe: Export xe_emit_aux_table_inv Tvrtko Ursulin
2025-08-19 8:55 ` [CI 07/13] drm/xe/xelp: Add AuxCCS invalidation to the indirect context workarounds Tvrtko Ursulin
2025-08-19 8:55 ` [CI 08/13] drm/xe: Flush GGTT writes after populating DPT Tvrtko Ursulin
2025-08-19 8:55 ` [CI 09/13] drm/xe: Handle DPT in system memory Tvrtko Ursulin
2025-08-19 8:55 ` [CI 10/13] drm/xe/display: Add support for AuxCCS Tvrtko Ursulin
2025-08-19 8:55 ` [CI 11/13] drm/xe: Force flush system memory AuxCCS data before scan out Tvrtko Ursulin
2025-08-19 8:55 ` [CI 12/13] late flush Tvrtko Ursulin
2025-08-19 8:55 ` [CI 13/13] drm/i915/display: Expose AuxCCS frame buffer modifiers for Xe Tvrtko Ursulin
2025-08-19 14:16 ` ✗ CI.checkpatch: warning for auxccs late flush Patchwork
2025-08-19 14:17 ` ✓ CI.KUnit: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-08-19 14:38 [CI 00/13] " 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=20250819085537.97902-1-tvrtko.ursulin@igalia.com \
--to=tvrtko.ursulin@igalia.com \
--cc=intel-xe@lists.freedesktop.org \
/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