From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH v2 1/2] drm/xe/svm: Ensure data will be migrated to system if indicated by madvise.
Date: Fri, 10 Oct 2025 16:20:20 +0530 [thread overview]
Message-ID: <4b6a94b0-2b19-4dbd-8436-87d9ed145dca@intel.com> (raw)
In-Reply-To: <20251010104149.72783-2-thomas.hellstrom@linux.intel.com>
On 10-10-2025 16:11, Thomas Hellström wrote:
> If the location madvise() is set to
> DRM_XE_PREFERRED_LOC_DEFAULT_SYSTEM, the drm_pagemap in the
> SVM gpu fault handler will be set to NULL. However there is nothing
> that explicitly migrates the data to system if it is already present
> in device memory.
>
> In that case, set the device memory owner to NULL to ensure
> data gets properly migrated to system on page-fault.
>
> v2:
> - Remove redundant dpagemap assignment (Himal Prasad Ghimiray)
Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
>
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Reviewed-by: Matthew Brost <matthew.brost@intel.com> #v1
> ---
> drivers/gpu/drm/xe/xe_svm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_svm.c b/drivers/gpu/drm/xe/xe_svm.c
> index 7e2db71ff34e..ef8c7aa485b5 100644
> --- a/drivers/gpu/drm/xe/xe_svm.c
> +++ b/drivers/gpu/drm/xe/xe_svm.c
> @@ -1034,6 +1034,9 @@ static int __xe_svm_handle_pagefault(struct xe_vm *vm, struct xe_vma *vma,
> if (err)
> return err;
>
> + dpagemap = xe_vma_resolve_pagemap(vma, tile);
> + if (!dpagemap && !ctx.devmem_only)
> + ctx.device_private_page_owner = NULL;
> range = xe_svm_range_find_or_insert(vm, fault_addr, vma, &ctx);
>
> if (IS_ERR(range))
> @@ -1054,7 +1057,6 @@ static int __xe_svm_handle_pagefault(struct xe_vm *vm, struct xe_vma *vma,
>
> range_debug(range, "PAGE FAULT");
>
> - dpagemap = xe_vma_resolve_pagemap(vma, tile);
> if (--migrate_try_count >= 0 &&
> xe_svm_range_needs_migrate_to_vram(range, vma, !!dpagemap || ctx.devmem_only)) {
> ktime_t migrate_start = xe_svm_stats_ktime_get();
next prev parent reply other threads:[~2025-10-10 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 10:41 [PATCH v2 0/2] SVM migration fixes Thomas Hellström
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 [this message]
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=4b6a94b0-2b19-4dbd-8436-87d9ed145dca@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--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