From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: daniele.ceraolospurio@intel.com, carlos.santa@intel.com,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: [PATCH] drm/xe: Validate preferred system memory placement in xe_svm_range_validate
Date: Tue, 6 Jan 2026 13:34:43 -0800 [thread overview]
Message-ID: <20260106213443.1866797-1-matthew.brost@intel.com> (raw)
Ensure preferred system memory placement is checked in
xe_svm_range_validate when dpagemap is NULL. Without this check, a
prefetch to system memory may become a no-op because device memory is
considered a valid placement.
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Fixes: 238dbc9d9f4a ("drm/xe: Use the vma attibute drm_pagemap to select where to migrate")
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/xe/xe_svm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_svm.c b/drivers/gpu/drm/xe/xe_svm.c
index 05dba6abbcc8..be55b53ace8c 100644
--- a/drivers/gpu/drm/xe/xe_svm.c
+++ b/drivers/gpu/drm/xe/xe_svm.c
@@ -988,6 +988,8 @@ bool xe_svm_range_validate(struct xe_vm *vm,
ret = (range->tile_present & ~range->tile_invalidated & tile_mask) == tile_mask;
if (dpagemap)
ret = ret && xe_svm_range_has_pagemap_locked(range, dpagemap);
+ else
+ ret = ret && !range->base.pages.dpagemap;
xe_svm_notifier_unlock(vm);
--
2.34.1
next reply other threads:[~2026-01-06 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 21:34 Matthew Brost [this message]
2026-01-06 22:35 ` ✓ CI.KUnit: success for drm/xe: Validate preferred system memory placement in xe_svm_range_validate Patchwork
2026-01-06 23:20 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-07 1:57 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-07 6:26 ` [PATCH] " Ghimiray, Himal Prasad
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=20260106213443.1866797-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=carlos.santa@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.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