Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH v4 0/8] Replace xe_hmm with gpusvm
Date: Mon, 12 May 2025 16:06:38 +0100	[thread overview]
Message-ID: <20250512150637.61462-10-matthew.auld@intel.com> (raw)

As a first step to moving userptr handling over to drm, replace the hmm
usage in xe over to gpusvm, which already offers similar functionality. As
some prep steps we also align on some of the missing pieces that were
already handled in xe_hmm.

v2:
  - Rework the gpusvm API based on feedback.
  - Unify SVM and userptr vm struct so we use the same notifier lock.
  - Drop the mark pages as dirty patch.
  - Various other improvements.
v3:
  - Further unify common handling of userptr and svm in xe.
v4:
  - Allow building xe without userptr, like when building on UML.

-- 
2.49.0


             reply	other threads:[~2025-05-12 15:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 15:06 Matthew Auld [this message]
2025-05-12 15:06 ` [PATCH v4 1/8] drm/gpusvm: fix hmm_pfn_to_map_order() usage Matthew Auld
2025-05-12 15:06 ` [PATCH v4 2/8] drm/gpusvm: use more selective dma dir in get_pages() Matthew Auld
2025-05-12 15:06 ` [PATCH v4 3/8] drm/gpusvm: pull out drm_gpusvm_pages substructure Matthew Auld
2025-05-12 15:06 ` [PATCH v4 4/8] drm/gpusvm: refactor core API to use pages struct Matthew Auld
2025-05-12 15:06 ` [PATCH v4 5/8] drm/gpusvm: export drm_gpusvm_pages API Matthew Auld
2025-05-12 15:06 ` [PATCH v4 6/8] drm/xe/vm: split userptr bits into separate file Matthew Auld
2025-06-09 17:05   ` Matthew Brost
2025-05-12 15:06 ` [PATCH v4 7/8] drm/xe/userptr: replace xe_hmm with gpusvm Matthew Auld
2025-06-09 17:09   ` Matthew Brost
2025-05-12 15:06 ` [PATCH v4 8/8] drm/xe/pt: unify xe_pt_svm_pre_commit with userptr Matthew Auld
2025-05-12 16:27 ` ✓ CI.Patch_applied: success for Replace xe_hmm with gpusvm (rev4) Patchwork
2025-05-12 16:27 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-12 16:28 ` ✓ CI.KUnit: success " Patchwork
2025-05-12 16:38 ` ✗ CI.Build: failure " Patchwork
2025-05-13 11:04 ` ✗ CI.Patch_applied: " Patchwork
2025-05-26 21:59 ` 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=20250512150637.61462-10-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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