From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/2] Use DRM_GPUVM helpers for the vm evict and exobj listss
Date: Sat, 9 Dec 2023 15:49:15 +0100 [thread overview]
Message-ID: <20231209144917.4459-1-thomas.hellstrom@linux.intel.com> (raw)
The first patch replaces our driver-specific code with calls to DRM_GPUVM,
and selects to use the DRM_GPUVM fine-grained locking.
The second patch sets a flag that makes DRM_GPUVM assume dma_resv locking
instead, that we've previously using in the Xe driver.
Thomas Hellström (2):
drm/xe: Use DRM GPUVM helpers for external- and evicted objects
drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm
drivers/gpu/drm/xe/xe_bo.c | 63 +++----
drivers/gpu/drm/xe/xe_exec.c | 72 ++------
drivers/gpu/drm/xe/xe_vm.c | 296 ++++++++-----------------------
drivers/gpu/drm/xe/xe_vm.h | 13 +-
drivers/gpu/drm/xe/xe_vm_types.h | 67 ++-----
5 files changed, 122 insertions(+), 389 deletions(-)
--
2.42.0
next reply other threads:[~2023-12-09 14:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 14:49 Thomas Hellström [this message]
2023-12-09 14:49 ` [PATCH 1/2] drm/xe: Use DRM GPUVM helpers for external- and evicted objects Thomas Hellström
2023-12-11 21:24 ` Rodrigo Vivi
2023-12-11 23:08 ` Matthew Brost
2023-12-12 8:29 ` Thomas Hellström
2023-12-09 14:49 ` [PATCH 2/2] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm Thomas Hellström
2023-12-11 21:24 ` Rodrigo Vivi
2023-12-09 14:51 ` ✓ CI.Patch_applied: success for Use DRM_GPUVM helpers for the vm evict and exobj listss Patchwork
2023-12-09 14:52 ` ✓ CI.checkpatch: " Patchwork
2023-12-09 14:53 ` ✓ CI.KUnit: " Patchwork
2023-12-09 15:00 ` ✓ CI.Build: " Patchwork
2023-12-09 15:00 ` ✓ CI.Hooks: " Patchwork
2023-12-09 15:02 ` ✓ CI.checksparse: " Patchwork
2023-12-09 15:39 ` ✗ CI.BAT: failure " 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=20231209144917.4459-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--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