From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: francois.dugast@intel.com, daniele.ceraolospurio@intel.com,
michal.wajdeczko@intel.com
Subject: [PATCH v2 0/2] GuC CT memory optimizations
Date: Fri, 13 Feb 2026 13:16:23 -0800 [thread overview]
Message-ID: <20260213211625.3117729-1-matthew.brost@intel.com> (raw)
Profiling has shown that reading from VRAM on BMG is very slow and
introduces significant latency in GuC CT operations. To address this,
CPU-side read buffers (G2H) are moved to system memory, and unnecessary
CPU reads of VRAM in hot paths are removed. This is marked as a fixes
change due to the dramatic improvement in G2H performance, which affects
hot paths such as TLB invalidation fences and fault-storm handling.
We likely have similar issues in hardware fence signaling paths that
currently read from VRAM. A follow-up will move the LRC fence seqno (and
possibly other CPU-side LRC reads) to system memory as well.
v2:
- Fix devcoredump explosion (Testing)
Matt
Matthew Brost (2):
drm/xe: Split H2G and G2H into separate buffer objects
drm/xe: Remove H2G reads in CT send path in non-debug builds
drivers/gpu/drm/xe/xe_guc_ct.c | 80 ++++++++++++++++++----------
drivers/gpu/drm/xe/xe_guc_ct_types.h | 6 ++-
2 files changed, 55 insertions(+), 31 deletions(-)
--
2.34.1
next reply other threads:[~2026-02-13 21:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 21:16 Matthew Brost [this message]
2026-02-13 21:16 ` [PATCH v2 1/2] drm/xe: Split H2G and G2H into separate buffer objects Matthew Brost
2026-02-13 22:55 ` Michal Wajdeczko
2026-02-14 0:54 ` Matthew Brost
2026-02-17 16:44 ` Matthew Brost
2026-02-13 21:16 ` [PATCH v2 2/2] drm/xe: Remove H2G reads in CT send path in non-debug builds Matthew Brost
2026-02-16 12:51 ` Francois Dugast
2026-02-16 17:40 ` Matthew Brost
2026-02-17 11:19 ` Francois Dugast
2026-02-18 0:24 ` Summers, Stuart
2026-02-18 2:35 ` Matthew Brost
2026-02-13 21:59 ` ✓ CI.KUnit: success for GuC CT memory optimizations Patchwork
2026-02-13 22:39 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-14 21:35 ` ✗ 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=20260213211625.3117729-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@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