Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: daniele.ceraolospurio@intel.com, carlos.santa@intel.com,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH] drm/xe: Validate preferred system memory placement in xe_svm_range_validate
Date: Wed, 7 Jan 2026 11:56:28 +0530	[thread overview]
Message-ID: <ad086252-f93a-4a96-a63e-7b2a09aaef0e@intel.com> (raw)
In-Reply-To: <20260106213443.1866797-1-matthew.brost@intel.com>



On 07-01-2026 03:04, Matthew Brost wrote:
> 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;

LGTM.
Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>

>   
>   	xe_svm_notifier_unlock(vm);
>   


      parent reply	other threads:[~2026-01-07  6:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 21:34 [PATCH] drm/xe: Validate preferred system memory placement in xe_svm_range_validate Matthew Brost
2026-01-06 22:35 ` ✓ CI.KUnit: success for " 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 ` Ghimiray, Himal Prasad [this message]

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=ad086252-f93a-4a96-a63e-7b2a09aaef0e@intel.com \
    --to=himal.prasad.ghimiray@intel.com \
    --cc=carlos.santa@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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