From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [CI 00/13] CCS uncached mocs 0 test run
Date: Thu, 2 Oct 2025 10:45:22 -0400 [thread overview]
Message-ID: <aN6QAvE0zQHy_1Rj@intel.com> (raw)
In-Reply-To: <20251002142453.25574-1-tvrtko.ursulin@igalia.com>
On Thu, Oct 02, 2025 at 03:24:38PM +0100, Tvrtko Ursulin wrote:
> HW hardcodes mocs 0 for CCS?!
>
> Tvrtko Ursulin (13):
> drm/xe: Fix ggtt fb alignment
> 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
> mocs 0 uncached
what is this?
> drm/i915/display: Expose AuxCCS frame buffer modifiers for Xe
>
> .../drm/i915/display/skl_universal_plane.c | 6 -
> drivers/gpu/drm/xe/display/xe_fb_pin.c | 159 ++++++++---
> .../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_lrc.c | 38 +++
> drivers/gpu/drm/xe/xe_mocs.c | 247 ++++++++++--------
> drivers/gpu/drm/xe/xe_ring_ops.c | 164 ++++++------
> drivers/gpu/drm/xe/xe_ring_ops.h | 3 +
> drivers/gpu/drm/xe/xe_ring_ops_types.h | 2 +-
> 10 files changed, 400 insertions(+), 227 deletions(-)
>
> --
> 2.48.0
>
next prev parent reply other threads:[~2025-10-02 14:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 14:24 [CI 00/13] CCS uncached mocs 0 test run Tvrtko Ursulin
2025-10-02 14:24 ` [CI 01/13] drm/xe: Fix ggtt fb alignment Tvrtko Ursulin
2025-10-02 14:24 ` [CI 02/13] drm/xe/xelpg: Flush CCS when flushing caches Tvrtko Ursulin
2025-10-02 14:24 ` [CI 03/13] drm/xe/xelp: Quiesce memory traffic before invalidating AuxCCS Tvrtko Ursulin
2025-10-02 14:24 ` [CI 04/13] drm/xe/xelp: Support auxccs invalidation on blitter Tvrtko Ursulin
2025-10-02 14:24 ` [CI 05/13] drm/xe/xelp: Use MI_FLUSH_DW_CCS on auxccs platforms Tvrtko Ursulin
2025-10-02 14:24 ` [CI 06/13] drm/xe/xelp: Wait for AuxCCS invalidation to complete Tvrtko Ursulin
2025-10-02 14:24 ` [CI 07/13] drm/xe: Export xe_emit_aux_table_inv Tvrtko Ursulin
2025-10-02 14:24 ` [CI 08/13] drm/xe/xelp: Add AuxCCS invalidation to the indirect context workarounds Tvrtko Ursulin
2025-10-02 14:24 ` [CI 09/13] drm/xe: Flush GGTT writes after populating DPT Tvrtko Ursulin
2025-10-02 14:24 ` [CI 10/13] drm/xe: Handle DPT in system memory Tvrtko Ursulin
2025-10-02 14:24 ` [CI 11/13] drm/xe/display: Add support for AuxCCS Tvrtko Ursulin
2025-10-02 14:24 ` [CI 12/13] mocs 0 uncached Tvrtko Ursulin
2025-10-02 14:24 ` [CI 13/13] drm/i915/display: Expose AuxCCS frame buffer modifiers for Xe Tvrtko Ursulin
2025-10-02 14:42 ` ✗ CI.checkpatch: warning for CCS uncached mocs 0 test run Patchwork
2025-10-02 14:43 ` ✓ CI.KUnit: success " Patchwork
2025-10-02 14:45 ` Rodrigo Vivi [this message]
2025-10-02 17:11 ` [CI 00/13] " Tvrtko Ursulin
2025-10-02 15:19 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-10-02 16:46 ` ✗ Xe.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=aN6QAvE0zQHy_1Rj@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tvrtko.ursulin@igalia.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.