Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Drop xe_mark_range_accessed in HMM layer
Date: Wed, 09 Oct 2024 09:36:49 +0200	[thread overview]
Message-ID: <824201591dfbd8fd2f9595720156121478b3a4b0.camel@linux.intel.com> (raw)
In-Reply-To: <20240909182128.585364-1-matthew.brost@intel.com>

On Mon, 2024-09-09 at 11:21 -0700, Matthew Brost wrote:
> Not needed as hmm_range_fault does this and also as pages returned
> from
> hmm_range_fault could move while mmap lock is dropped and not not
> holding notifier lock. Page corruption showed up in similar code
> paths
> in SVM work.
> 
> Fixes: 81e058a3e7fd ("drm/xe: Introduce helper to populate userptr")
> Suggested-by: Simona Vetter <simona.vetter@ffwll.ch>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

I wonder whether you can add something like "Write-enabled
hmm_range_fault() always ensures CPU ptes are marked dirty for the page
."

Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>


> ---
>  drivers/gpu/drm/xe/xe_hmm.c | 25 -------------------------
>  1 file changed, 25 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_hmm.c
> b/drivers/gpu/drm/xe/xe_hmm.c
> index 2c32dc46f7d4..dde80a66c9aa 100644
> --- a/drivers/gpu/drm/xe/xe_hmm.c
> +++ b/drivers/gpu/drm/xe/xe_hmm.c
> @@ -19,30 +19,6 @@ static u64 xe_npages_in_range(unsigned long start,
> unsigned long end)
>  	return (end - start) >> PAGE_SHIFT;
>  }
>  
> -/*
> - * xe_mark_range_accessed() - mark a range is accessed, so core mm
> - * have such information for memory eviction or write back to
> - * hard disk
> - *
> - * @range: the range to mark
> - * @write: if write to this range, we mark pages in this range
> - * as dirty
> - */
> -static void xe_mark_range_accessed(struct hmm_range *range, bool
> write)
> -{
> -	struct page *page;
> -	u64 i, npages;
> -
> -	npages = xe_npages_in_range(range->start, range->end);
> -	for (i = 0; i < npages; i++) {
> -		page = hmm_pfn_to_page(range->hmm_pfns[i]);
> -		if (write)
> -			set_page_dirty_lock(page);
> -
> -		mark_page_accessed(page);
> -	}
> -}
> -
>  /*
>   * xe_build_sg() - build a scatter gather table for all the physical
> pages/pfn
>   * in a hmm_range. dma-map pages if necessary. dma-address is save
> in sg table
> @@ -242,7 +218,6 @@ int xe_hmm_userptr_populate_range(struct
> xe_userptr_vma *uvma,
>  	if (ret)
>  		goto free_pfns;
>  
> -	xe_mark_range_accessed(&hmm_range, write);
>  	userptr->sg = &userptr->sgt;
>  	userptr->notifier_seq = hmm_range.notifier_seq;
>  


      parent reply	other threads:[~2024-10-09  7:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 18:21 [PATCH] drm/xe: Drop xe_mark_range_accessed in HMM layer Matthew Brost
2024-09-09 18:25 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-09 18:26 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-09 18:27 ` ✓ CI.KUnit: success " Patchwork
2024-09-09 18:43 ` ✓ CI.Build: " Patchwork
2024-09-09 18:47 ` ✓ CI.Hooks: " Patchwork
2024-09-09 18:49 ` ✓ CI.checksparse: " Patchwork
2024-09-09 19:32 ` ✓ CI.BAT: " Patchwork
2024-09-09 23:25 ` ✓ CI.FULL: " Patchwork
2024-10-09  7:36 ` Thomas Hellström [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=824201591dfbd8fd2f9595720156121478b3a4b0.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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