From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/xe: Move DSB l2 flush to a more sensible place
Date: Fri, 6 Jun 2025 16:19:04 +0100 [thread overview]
Message-ID: <097aa0d8-6bc1-4616-8f8f-805b7fc5e886@intel.com> (raw)
In-Reply-To: <20250606104546.1996818-3-matthew.auld@intel.com>
On 06/06/2025 11:45, Matthew Auld wrote:
> From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>
> Flushing l2 is only needed after all data has been written.
>
> Fixes: 01570b446939 ("drm/xe/bmg: implement Wa_16023588340")
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: <stable@vger.kernel.org> # v6.12+
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Tested this locally and noticed a pretty big improvement just playing
around in the desktop environment, where stuff feels way smoother.
> ---
> drivers/gpu/drm/xe/display/xe_dsb_buffer.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_dsb_buffer.c b/drivers/gpu/drm/xe/display/xe_dsb_buffer.c
> index f95375451e2f..9f941fc2e36b 100644
> --- a/drivers/gpu/drm/xe/display/xe_dsb_buffer.c
> +++ b/drivers/gpu/drm/xe/display/xe_dsb_buffer.c
> @@ -17,10 +17,7 @@ u32 intel_dsb_buffer_ggtt_offset(struct intel_dsb_buffer *dsb_buf)
>
> void intel_dsb_buffer_write(struct intel_dsb_buffer *dsb_buf, u32 idx, u32 val)
> {
> - struct xe_device *xe = dsb_buf->vma->bo->tile->xe;
> -
> iosys_map_wr(&dsb_buf->vma->bo->vmap, idx * 4, u32, val);
> - xe_device_l2_flush(xe);
> }
>
> u32 intel_dsb_buffer_read(struct intel_dsb_buffer *dsb_buf, u32 idx)
> @@ -30,12 +27,9 @@ u32 intel_dsb_buffer_read(struct intel_dsb_buffer *dsb_buf, u32 idx)
>
> void intel_dsb_buffer_memset(struct intel_dsb_buffer *dsb_buf, u32 idx, u32 val, size_t size)
> {
> - struct xe_device *xe = dsb_buf->vma->bo->tile->xe;
> -
> WARN_ON(idx > (dsb_buf->buf_size - size) / sizeof(*dsb_buf->cmd_buf));
>
> iosys_map_memset(&dsb_buf->vma->bo->vmap, idx * 4, val, size);
> - xe_device_l2_flush(xe);
> }
>
> bool intel_dsb_buffer_create(struct intel_crtc *crtc, struct intel_dsb_buffer *dsb_buf, size_t size)
> @@ -74,9 +68,12 @@ void intel_dsb_buffer_cleanup(struct intel_dsb_buffer *dsb_buf)
>
> void intel_dsb_buffer_flush_map(struct intel_dsb_buffer *dsb_buf)
> {
> + struct xe_device *xe = dsb_buf->vma->bo->tile->xe;
> +
> /*
> * The memory barrier here is to ensure coherency of DSB vs MMIO,
> * both for weak ordering archs and discrete cards.
> */
> - xe_device_wmb(dsb_buf->vma->bo->tile->xe);
> + xe_device_wmb(xe);
> + xe_device_l2_flush(xe);
> }
next prev parent reply other threads:[~2025-06-06 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 10:45 [PATCH 1/2] drm/xe: Move DSB l2 flush to a more sensible place Matthew Auld
2025-06-06 10:45 ` [PATCH 2/2] drm/xe: move DPT " Matthew Auld
2025-06-17 16:35 ` Ville Syrjälä
2025-06-18 18:59 ` Lucas De Marchi
2025-06-06 15:19 ` Matthew Auld [this message]
2025-06-17 16:26 ` [PATCH 1/2] drm/xe: Move DSB " Ville Syrjälä
2025-06-18 19:06 ` Lucas De Marchi
2025-06-24 17:47 ` Lucas De Marchi
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=097aa0d8-6bc1-4616-8f8f-805b7fc5e886@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=stable@vger.kernel.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