From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [RFC PATCH 0/2] LNL_FLUSH_* enhancements
Date: Wed, 22 Jul 2026 14:59:33 -0700 [thread overview]
Message-ID: <20260722215935.1369012-1-matthew.brost@intel.com> (raw)
The LNL_FLUSH_* workaround is a horrid hack that has been papering over
bugs. Let's limit its scope to determine whether it is actually needed
on newer platforms and add more debug information for cases where it
still occurs.
This came up again in the context of this series [1].
Matt
[1] https://patchwork.freedesktop.org/series/170916/
Matthew Brost (2):
drm/xe: Scope LNL_FLUSH_* workaround to affected CPUs, not GPU
platform
drm/xe: Add DRM_XE_DEBUG_FLUSH_WA to force the CPU flush workaround on
drivers/gpu/drm/xe/Kconfig.debug | 16 ++++++
drivers/gpu/drm/xe/Makefile | 1 +
drivers/gpu/drm/xe/xe_cpu_info.c | 67 +++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_cpu_info.h | 13 +++++
drivers/gpu/drm/xe/xe_device.h | 35 +++++++++----
drivers/gpu/drm/xe/xe_device_types.h | 10 ++++
drivers/gpu/drm/xe/xe_guc_ct.c | 56 +++++++++++++++++++--
drivers/gpu/drm/xe/xe_guc_ct.h | 1 +
drivers/gpu/drm/xe/xe_guc_tlb_inval.c | 2 +-
drivers/gpu/drm/xe/xe_pci.c | 10 ++++
drivers/gpu/drm/xe/xe_tlb_inval.c | 28 +++++++++++
drivers/gpu/drm/xe/xe_wait_user_fence.c | 6 ++-
12 files changed, 228 insertions(+), 17 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_cpu_info.c
create mode 100644 drivers/gpu/drm/xe/xe_cpu_info.h
--
2.34.1
next reply other threads:[~2026-07-22 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 21:59 Matthew Brost [this message]
2026-07-22 21:59 ` [RFC PATCH 1/2] drm/xe: Scope LNL_FLUSH_* workaround to affected CPUs, not GPU platform Matthew Brost
2026-07-22 21:59 ` [RFC PATCH 2/2] drm/xe: Add DRM_XE_DEBUG_FLUSH_WA to force the CPU flush workaround on Matthew Brost
2026-07-22 23:45 ` ✗ CI.checkpatch: warning for LNL_FLUSH_* enhancements Patchwork
2026-07-22 23:46 ` ✓ CI.KUnit: success " Patchwork
2026-07-23 0:20 ` ✓ Xe.CI.BAT: " 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=20260722215935.1369012-1-matthew.brost@intel.com \
--to=matthew.brost@intel.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 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.