From: Matthew Brost <matthew.brost@intel.com>
To: Oak Zeng <oak.zeng@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <thomas.hellstrom@intel.com>,
<airlied@gmail.com>, <brian.welty@intel.com>,
<himal.prasad.ghimiray@intel.com>
Subject: Re: [PATCH 5/5] drm/xe: Use hmm_range_fault to populate user pages
Date: Thu, 14 Mar 2024 20:54:43 +0000 [thread overview]
Message-ID: <ZfNkE9phLoW5e2Y1@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240314033553.1379444-6-oak.zeng@intel.com>
On Wed, Mar 13, 2024 at 11:35:53PM -0400, Oak Zeng wrote:
> This is an effort to unify hmmptr (aka system allocator)
> and userptr code. hmm_range_fault is used to populate
> a virtual address range for both hmmptr and userptr,
> instead of hmmptr using hmm_range_fault and userptr
> using get_user_pages_fast.
>
> This also aligns with AMD gpu driver's behavior. In
> long term, we plan to put some common helpers in this
> area to drm layer so it can be re-used by different
> vendors.
>
> Signed-off-by: Oak Zeng <oak.zeng@intel.com>
> ---
> drivers/gpu/drm/xe/xe_vm.c | 105 ++-----------------------------------
> 1 file changed, 4 insertions(+), 101 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index db3f049a47dc..d6088dcac74a 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -38,6 +38,7 @@
> #include "xe_sync.h"
> #include "xe_trace.h"
> #include "xe_wa.h"
> +#include "xe_hmm.h"
>
> static struct drm_gem_object *xe_vm_obj(struct xe_vm *vm)
> {
> @@ -65,113 +66,15 @@ int xe_vma_userptr_check_repin(struct xe_userptr_vma *uvma)
>
> int xe_vma_userptr_pin_pages(struct xe_userptr_vma *uvma)
See my comments in the previous patch about layer, those comments are
valid here too.
> {
> - struct xe_userptr *userptr = &uvma->userptr;
> struct xe_vma *vma = &uvma->vma;
> struct xe_vm *vm = xe_vma_vm(vma);
> struct xe_device *xe = vm->xe;
> - const unsigned long num_pages = xe_vma_size(vma) >> PAGE_SHIFT;
> - struct page **pages;
> - bool in_kthread = !current->mm;
> - unsigned long notifier_seq;
> - int pinned, ret, i;
> - bool read_only = xe_vma_read_only(vma);
> + bool write = !xe_vma_read_only(vma);
> + struct hmm_range hmm_range;
>
> lockdep_assert_held(&vm->lock);
> xe_assert(xe, xe_vma_is_userptr(vma));
> -retry:
> - if (vma->gpuva.flags & XE_VMA_DESTROYED)
> - return 0;
^^^
This should not be dropped. Both the vma->gpuva.flags & XE_VMA_DESTROYED
and userptr invalidation check retry loop should still be in here.
> -
> - notifier_seq = mmu_interval_read_begin(&userptr->notifier);
> - if (notifier_seq == userptr->notifier_seq)
> - return 0;
> -
> - pages = kvmalloc_array(num_pages, sizeof(*pages), GFP_KERNEL);
> - if (!pages)
> - return -ENOMEM;
> -
> - if (userptr->sg) {
> - dma_unmap_sgtable(xe->drm.dev,
> - userptr->sg,
> - read_only ? DMA_TO_DEVICE :
> - DMA_BIDIRECTIONAL, 0);
> - sg_free_table(userptr->sg);
> - userptr->sg = NULL;
> - }
^^^
Likewise, I don't think this should be dropped either.
> -
> - pinned = ret = 0;
> - if (in_kthread) {
> - if (!mmget_not_zero(userptr->notifier.mm)) {
> - ret = -EFAULT;
> - goto mm_closed;
> - }
> - kthread_use_mm(userptr->notifier.mm);
> - }
^^^
Nor this.
> -
> - while (pinned < num_pages) {
> - ret = get_user_pages_fast(xe_vma_userptr(vma) +
> - pinned * PAGE_SIZE,
> - num_pages - pinned,
> - read_only ? 0 : FOLL_WRITE,
> - &pages[pinned]);
> - if (ret < 0)
> - break;
> -
> - pinned += ret;
> - ret = 0;
> - }
^^^
We should be replacing this.
> -
> - if (in_kthread) {
> - kthread_unuse_mm(userptr->notifier.mm);
> - mmput(userptr->notifier.mm);
> - }
> -mm_closed:
> - if (ret)
> - goto out;
> -
> - ret = sg_alloc_table_from_pages_segment(&userptr->sgt, pages,
> - pinned, 0,
> - (u64)pinned << PAGE_SHIFT,
> - xe_sg_segment_size(xe->drm.dev),
> - GFP_KERNEL);
> - if (ret) {
> - userptr->sg = NULL;
> - goto out;
> - }
> - userptr->sg = &userptr->sgt;
> -
> - ret = dma_map_sgtable(xe->drm.dev, userptr->sg,
> - read_only ? DMA_TO_DEVICE :
> - DMA_BIDIRECTIONAL,
> - DMA_ATTR_SKIP_CPU_SYNC |
> - DMA_ATTR_NO_KERNEL_MAPPING);
> - if (ret) {
> - sg_free_table(userptr->sg);
> - userptr->sg = NULL;
> - goto out;
> - }
> -
> - for (i = 0; i < pinned; ++i) {
> - if (!read_only) {
> - lock_page(pages[i]);
> - set_page_dirty(pages[i]);
> - unlock_page(pages[i]);
> - }
> -
> - mark_page_accessed(pages[i]);
> - }
> -
> -out:
> - release_pages(pages, pinned);
> - kvfree(pages);
^^^
Through here (minus existing the kthread) with hmm call. I guess the
kthread enter / exit could be in the hmm layer too.
Matt
> -
> - if (!(ret < 0)) {
> - userptr->notifier_seq = notifier_seq;
> - if (xe_vma_userptr_check_repin(uvma) == -EAGAIN)
> - goto retry;
> - }
> -
> - return ret < 0 ? ret : 0;
> + return xe_hmm_populate_range(vma, &hmm_range, write);
> }
>
> static bool preempt_fences_waiting(struct xe_vm *vm)
> --
> 2.26.3
>
next prev parent reply other threads:[~2024-03-14 20:55 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 3:35 [PATCH 0/5] Use hmm_range_fault to populate user page Oak Zeng
2024-03-14 3:28 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-14 3:28 ` ✗ CI.checkpatch: warning " Patchwork
2024-03-14 3:29 ` ✗ CI.KUnit: failure " Patchwork
2024-03-14 3:35 ` [PATCH 1/5] drm/xe/svm: Remap and provide memmap backing for GPU vram Oak Zeng
2024-03-14 17:17 ` Matthew Brost
2024-03-14 18:32 ` Zeng, Oak
2024-03-14 20:49 ` Matthew Brost
2024-03-15 16:00 ` Zeng, Oak
2024-03-15 20:39 ` Matthew Brost
2024-03-15 21:31 ` Zeng, Oak
2024-03-16 1:25 ` Matthew Brost
2024-03-18 10:16 ` Hellstrom, Thomas
2024-03-18 15:02 ` Zeng, Oak
2024-03-18 15:46 ` Hellstrom, Thomas
2024-03-18 14:51 ` Zeng, Oak
2024-03-15 1:45 ` Welty, Brian
2024-03-15 3:10 ` Zeng, Oak
2024-03-15 3:16 ` Zeng, Oak
2024-03-15 18:05 ` Welty, Brian
2024-03-15 23:11 ` Zeng, Oak
2024-03-14 3:35 ` [PATCH 2/5] drm/xe: Helper to get memory region from tile Oak Zeng
2024-03-14 17:33 ` Matthew Brost
2024-03-14 17:44 ` Matthew Brost
2024-03-15 2:48 ` Zeng, Oak
2024-03-14 3:35 ` [PATCH 3/5] drm/xe: Helper to get dpa from pfn Oak Zeng
2024-03-14 17:39 ` Matthew Brost
2024-03-15 17:29 ` Zeng, Oak
2024-03-16 1:33 ` Matthew Brost
2024-03-18 19:25 ` Zeng, Oak
2024-03-18 12:09 ` Hellstrom, Thomas
2024-03-18 19:27 ` Zeng, Oak
2024-03-14 3:35 ` [PATCH 4/5] drm/xe: Helper to populate a userptr or hmmptr Oak Zeng
2024-03-14 20:25 ` Matthew Brost
2024-03-16 1:35 ` Zeng, Oak
2024-03-18 0:29 ` Matthew Brost
2024-03-18 11:53 ` Hellstrom, Thomas
2024-03-18 19:50 ` Zeng, Oak
2024-03-19 8:41 ` Hellstrom, Thomas
2024-03-19 16:13 ` Zeng, Oak
2024-03-19 19:52 ` Hellstrom, Thomas
2024-03-19 20:01 ` Zeng, Oak
2024-03-18 13:12 ` Hellstrom, Thomas
2024-03-18 14:49 ` Zeng, Oak
2024-03-18 15:40 ` Hellstrom, Thomas
2024-03-18 16:09 ` Zeng, Oak
2024-03-14 3:35 ` [PATCH 5/5] drm/xe: Use hmm_range_fault to populate user pages Oak Zeng
2024-03-14 20:54 ` Matthew Brost [this message]
2024-03-19 2:36 ` Zeng, Oak
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=ZfNkE9phLoW5e2Y1@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=airlied@gmail.com \
--cc=brian.welty@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=oak.zeng@intel.com \
--cc=thomas.hellstrom@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