From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: [Intel-xe] [PATCH v6 0/6] GPUVA with no uAPI changes
Date: Fri, 7 Jul 2023 23:56:08 -0700 [thread overview]
Message-ID: <20230708065614.1754600-1-matthew.brost@intel.com> (raw)
The patches from [1] rebased + address review feedback which do not
include uAPI changes.
[1] https://patchwork.freedesktop.org/series/117156/
v2: Fix build error
v3: Fix lockdep splat CI caught
v4: Fix build error
v5: Pull in latest GPUVA versions
v6: Fix build error
Danilo Krummrich (2):
drm: manager to keep track of GPUs VA mappings
drm: debugfs: provide infrastructure to dump a DRM GPU VA space
Matthew Brost (4):
drm/xe: Ban a VM if rebind worker hits an error
drm/xe: Add helpers to hide struct xe_vma internals
drm/xe: Remove __xe_vm_bind forward declaration
drm/xe: Port Xe to GPUVA
Documentation/gpu/drm-mm.rst | 36 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/drm_debugfs.c | 40 +
drivers/gpu/drm/drm_gem.c | 3 +
drivers/gpu/drm/drm_gpuva_mgr.c | 1743 ++++++++++++++++
drivers/gpu/drm/xe/tests/xe_migrate.c | 2 +-
drivers/gpu/drm/xe/xe_bo.c | 9 +-
drivers/gpu/drm/xe/xe_device.c | 2 +-
drivers/gpu/drm/xe/xe_engine.c | 13 +
drivers/gpu/drm/xe/xe_exec.c | 8 +-
drivers/gpu/drm/xe/xe_gt_pagefault.c | 23 +-
drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 14 +-
drivers/gpu/drm/xe/xe_migrate.c | 10 +-
drivers/gpu/drm/xe/xe_pt.c | 128 +-
drivers/gpu/drm/xe/xe_pt.h | 2 +-
drivers/gpu/drm/xe/xe_trace.h | 15 +-
drivers/gpu/drm/xe/xe_vm.c | 1973 +++++++++----------
drivers/gpu/drm/xe/xe_vm.h | 106 +-
drivers/gpu/drm/xe/xe_vm_madvise.c | 90 +-
drivers/gpu/drm/xe/xe_vm_types.h | 183 +-
include/drm/drm_debugfs.h | 25 +
include/drm/drm_drv.h | 6 +
include/drm/drm_gem.h | 52 +
include/drm/drm_gpuva_mgr.h | 763 +++++++
24 files changed, 3993 insertions(+), 1254 deletions(-)
create mode 100644 drivers/gpu/drm/drm_gpuva_mgr.c
create mode 100644 include/drm/drm_gpuva_mgr.h
--
2.34.1
next reply other threads:[~2023-07-08 6:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 6:56 Matthew Brost [this message]
2023-07-08 6:56 ` [Intel-xe] [PATCH v6 1/6] drm/xe: Ban a VM if rebind worker hits an error Matthew Brost
2023-07-08 6:56 ` [Intel-xe] [PATCH v6 2/6] drm/xe: Add helpers to hide struct xe_vma internals Matthew Brost
2023-07-08 6:56 ` [Intel-xe] [PATCH v6 3/6] drm: manager to keep track of GPUs VA mappings Matthew Brost
2023-07-08 6:56 ` [Intel-xe] [PATCH v6 4/6] drm: debugfs: provide infrastructure to dump a DRM GPU VA space Matthew Brost
2023-07-08 6:56 ` [Intel-xe] [PATCH v6 5/6] drm/xe: Remove __xe_vm_bind forward declaration Matthew Brost
2023-07-08 6:56 ` [Intel-xe] [PATCH v6 6/6] drm/xe: Port Xe to GPUVA Matthew Brost
2023-07-08 6:58 ` [Intel-xe] ✓ CI.Patch_applied: success for GPUVA with no uAPI changes Patchwork
2023-07-08 6:59 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-08 7:00 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-08 7:04 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-08 7:04 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-08 7:05 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-07-08 7:51 ` [Intel-xe] ○ CI.BAT: info " 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=20230708065614.1754600-1-matthew.brost@intel.com \
--to=matthew.brost@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