From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/3] Elide clear on full SVM copies
Date: Tue, 29 Sep 2026 11:10:21 -0700 [thread overview]
Message-ID: <20260929181024.2743854-1-matthew.brost@intel.com> (raw)
Clearing a BO whose contents will be fully overwritten immediately afterward
provides little benefit and reduces page-fault and prefetch bandwidth.
Elide the initial clear for SVM-allocated BOs, and only perform a clear in
the copy_to_device vfunc when the CPU pages are not fully populated.
Matt
Matthew Brost (3):
drm/xe: Add XE_BO_FLAG_SKIP_CLEAR
drm/xe: Add xe_migrate_clear_vram
drm/xe: Do not clear SVM device memory allocations up front
drivers/gpu/drm/xe/xe_bo.c | 3 +
drivers/gpu/drm/xe/xe_bo.h | 1 +
drivers/gpu/drm/xe/xe_migrate.c | 89 +++++++++++++++++++
drivers/gpu/drm/xe/xe_migrate.h | 5 ++
drivers/gpu/drm/xe/xe_svm.c | 150 ++++++++++++++++++++++++++++++--
5 files changed, 241 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2026-09-29 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 18:10 Matthew Brost [this message]
2026-09-29 18:10 ` [PATCH 1/3] drm/xe: Add XE_BO_FLAG_SKIP_CLEAR Matthew Brost
2026-09-29 18:10 ` [PATCH 2/3] drm/xe: Add xe_migrate_clear_vram Matthew Brost
2026-09-29 18:10 ` [PATCH 3/3] drm/xe: Do not clear SVM device memory allocations up front Matthew Brost
2026-09-29 18:27 ` sashiko-bot
2026-09-29 18:31 ` Matthew Brost
2026-09-29 20:16 ` Summers, Stuart
2026-09-29 21:14 ` Matthew Brost
2026-09-29 22:05 ` Summers, Stuart
2026-09-29 23:21 ` Matthew Brost
2026-09-29 18:18 ` ✓ CI.KUnit: success for Elide clear on full SVM copies Patchwork
2026-09-29 19:36 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-30 0:17 ` ✗ 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=20260929181024.2743854-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.