From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Auld" <matthew.auld@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>
Subject: [PATCH v2 0/2] SVM migration fixes
Date: Fri, 10 Oct 2025 12:41:47 +0200 [thread overview]
Message-ID: <20251010104149.72783-1-thomas.hellstrom@linux.intel.com> (raw)
Two small migration fixes. The first patch ensures
data is migrated to system on faults when there is
an madvise for the system location.
The second allows userptr data that was put in VRAM
by SVM migration to remain in VRAM also for
userptr maps.
v2:
- Fix a redundant assignment.
- Remove a Fixes: tag.
Matthew Brost (1):
drm/xe: Allow mixed mappings for userptr
Thomas Hellström (1):
drm/xe/svm: Ensure data will be migrated to system if indicated by
madvise.
drivers/gpu/drm/drm_gpusvm.c | 6 ++++--
drivers/gpu/drm/xe/xe_svm.c | 4 +++-
drivers/gpu/drm/xe/xe_userptr.c | 4 +++-
include/drm/drm_gpusvm.h | 4 ++++
4 files changed, 14 insertions(+), 4 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-10 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 10:41 Thomas Hellström [this message]
2025-10-10 10:41 ` [PATCH v2 1/2] drm/xe/svm: Ensure data will be migrated to system if indicated by madvise Thomas Hellström
2025-10-10 10:50 ` Ghimiray, Himal Prasad
2025-10-10 10:41 ` [PATCH v2 2/2] drm/xe: Allow mixed mappings for userptr Thomas Hellström
2025-10-10 10:50 ` Ghimiray, Himal Prasad
2025-10-13 9:20 ` ✓ CI.KUnit: success for SVM migration fixes (rev3) Patchwork
2025-10-13 10:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-13 10:34 ` ✓ Xe.CI.Full: " 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=20251010104149.72783-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@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