From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: matthew.auld@intel.com, thomas.hellstrom@linux.intel.com
Subject: [PATCH v2 0/3] Fix non-contiguous VRAM BO access in Xe
Date: Fri, 18 Oct 2024 14:16:20 -0700 [thread overview]
Message-ID: <20241018211623.1367891-1-matthew.brost@intel.com> (raw)
Mapping a non-contiguous VRAM BO doesn't work, start to fix this.
A follow up series should cleanup any remaining mapping of
non-contiguous VRAM BOs, add non-visible access support to
xe_ttm_access_memory, and warn / error on mapping a BO which cannot be
mapped.
v2:
- Include missing local change
Matthew Brost (3):
drm/ttm: Add ttm_bo_access
drm/xe: Add xe_ttm_access_memory
drm/xe: Use ttm_bo_access in xe_vm_snapshot_capture_delayed
drivers/gpu/drm/ttm/ttm_bo_util.c | 85 +++++++++++++++++++++++++++++++
drivers/gpu/drm/ttm/ttm_bo_vm.c | 65 +----------------------
drivers/gpu/drm/xe/xe_bo.c | 57 +++++++++++++++++++--
drivers/gpu/drm/xe/xe_vm.c | 18 +++----
include/drm/ttm/ttm_bo.h | 2 +
5 files changed, 149 insertions(+), 78 deletions(-)
--
2.34.1
next reply other threads:[~2024-10-18 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 21:16 Matthew Brost [this message]
2024-10-18 21:16 ` [PATCH v2 1/3] drm/ttm: Add ttm_bo_access Matthew Brost
2024-10-18 21:16 ` [PATCH v2 2/3] drm/xe: Add xe_ttm_access_memory Matthew Brost
2024-10-18 21:16 ` [PATCH v2 3/3] drm/xe: Use ttm_bo_access in xe_vm_snapshot_capture_delayed Matthew Brost
2024-10-18 22:49 ` ✓ CI.Patch_applied: success for Fix non-contiguous VRAM BO access in Xe (rev2) Patchwork
2024-10-18 22:49 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-18 22:50 ` ✓ CI.KUnit: success " Patchwork
2024-10-18 23:02 ` ✓ CI.Build: " Patchwork
2024-10-18 23:04 ` ✓ CI.Hooks: " Patchwork
2024-10-18 23:06 ` ✗ CI.checksparse: warning " Patchwork
2024-10-18 23:26 ` ✗ CI.BAT: failure " Patchwork
2024-10-19 16:25 ` ✗ CI.FULL: " 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=20241018211623.1367891-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@linux.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