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 3/3] drm/xe: Use ttm_bo_access in xe_vm_snapshot_capture_delayed
Date: Fri, 18 Oct 2024 14:16:23 -0700 [thread overview]
Message-ID: <20241018211623.1367891-4-matthew.brost@intel.com> (raw)
In-Reply-To: <20241018211623.1367891-1-matthew.brost@intel.com>
Non-contiguous mapping of BO in VRAM doesn't work, use ttm_bo_access
instead.
v2:
- Fix error handling
Fixes: 0eb2a18a8fad ("drm/xe: Implement VM snapshot support for BO's and userptr")
Suggested-by: Matthew Auld <matthew.auld@intel.com>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/xe/xe_vm.c | 18 +++++++-----------
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
index c99380271de6..0f760fd69d44 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -3303,7 +3303,6 @@ void xe_vm_snapshot_capture_delayed(struct xe_vm_snapshot *snap)
for (int i = 0; i < snap->num_snaps; i++) {
struct xe_bo *bo = snap->snap[i].bo;
- struct iosys_map src;
int err;
if (IS_ERR(snap->snap[i].data))
@@ -3316,16 +3315,12 @@ void xe_vm_snapshot_capture_delayed(struct xe_vm_snapshot *snap)
}
if (bo) {
- xe_bo_lock(bo, false);
- err = ttm_bo_vmap(&bo->ttm, &src);
- if (!err) {
- xe_map_memcpy_from(xe_bo_device(bo),
- snap->snap[i].data,
- &src, snap->snap[i].bo_ofs,
- snap->snap[i].len);
- ttm_bo_vunmap(&bo->ttm, &src);
- }
- xe_bo_unlock(bo);
+ err = ttm_bo_access(&bo->ttm, snap->snap[i].bo_ofs,
+ snap->snap[i].data, snap->snap[i].len, 0);
+ if (!(err < 0) && err != snap->snap[i].len)
+ err = -EIO;
+ else if (!(err < 0))
+ err = 0;
} else {
void __user *userptr = (void __user *)(size_t)snap->snap[i].bo_ofs;
@@ -3375,6 +3370,7 @@ void xe_vm_snapshot_print(struct xe_vm_snapshot *snap, struct drm_printer *p)
u32 *val = snap->snap[i].data + j;
char dumped[ASCII85_BUFSZ];
+ printk("%s:%d: j=%d", __func__, __LINE__, (int)j);
drm_puts(p, ascii85_encode(*val, dumped));
}
--
2.34.1
next prev parent reply other threads:[~2024-10-18 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 21:16 [PATCH v2 0/3] Fix non-contiguous VRAM BO access in Xe Matthew Brost
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 ` Matthew Brost [this message]
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-4-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