Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	<thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH v3 4/6] drm/xe: Use ttm_bo_access in xe_vm_snapshot_capture_delayed
Date: Mon, 21 Oct 2024 16:58:43 +0000	[thread overview]
Message-ID: <ZxaIQy+RVf8qTjn1@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <3a956975-4e6b-4990-80e2-769872d17816@intel.com>

On Mon, Oct 21, 2024 at 10:07:31AM +0100, Matthew Auld wrote:
> On 19/10/2024 20:20, Matthew Brost wrote:
> > 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>
> 
> The other user looks to be the clear color stuff for display. See
> intel_bo_read_from_page(). I think that is also potentially busted?
> 

I looked at display but missed this. Will fix in next rev.

> > ---
> >   drivers/gpu/drm/xe/xe_vm.c | 17 ++++++-----------
> >   1 file changed, 6 insertions(+), 11 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> > index c99380271de6..c8782da3a5c3 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);
> 
> I think we still need the lock, or is that grabbed somewhere else? Also I
> guess CI doesn't currently hit this path?
> 

Yep. ttm_bo_access does a ttm_bo_reserve / ttm_bo_unreserve which is a
lock / unlock.

Matt

> > -			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;

  reply	other threads:[~2024-10-21 17:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 19:20 [PATCH v3 0/6] Fix non-contiguous VRAM BO access in Xe Matthew Brost
2024-10-19 19:20 ` [PATCH v3 1/6] drm/ttm: Add ttm_bo_access Matthew Brost
2024-10-19 19:20 ` [PATCH v3 2/6] drm/xe: Add xe_ttm_access_memory Matthew Brost
2024-10-19 19:20 ` [PATCH v3 3/6] drm/xe: Update xe_ttm_access_memory to use GPU for non-visible access Matthew Brost
2024-10-21 10:15   ` Matthew Auld
2024-10-21 11:01     ` Thomas Hellström
2024-10-21 17:18       ` Matthew Brost
2024-10-21 17:02     ` Matthew Brost
2024-10-19 19:20 ` [PATCH v3 4/6] drm/xe: Use ttm_bo_access in xe_vm_snapshot_capture_delayed Matthew Brost
2024-10-21  9:07   ` Matthew Auld
2024-10-21 16:58     ` Matthew Brost [this message]
2024-10-19 19:20 ` [PATCH v3 5/6] drm/xe: Set XE_BO_FLAG_PINNED in migrate selftest BOs Matthew Brost
2024-10-21  9:50   ` Matthew Auld
2024-10-19 19:20 ` [PATCH v3 6/6] drm/xe: Only allow contiguous BOs to use xe_bo_vmap Matthew Brost
2024-10-21  9:32   ` Matthew Auld
2024-10-19 19:25 ` ✓ CI.Patch_applied: success for Fix non-contiguous VRAM BO access in Xe (rev3) Patchwork
2024-10-19 19:25 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-19 19:27 ` ✓ CI.KUnit: success " Patchwork
2024-10-19 19:38 ` ✓ CI.Build: " Patchwork
2024-10-19 19:40 ` ✓ CI.Hooks: " Patchwork
2024-10-19 19:42 ` ✗ CI.checksparse: warning " Patchwork
2024-10-19 20:07 ` ✓ CI.BAT: success " Patchwork
2024-10-19 21:06 ` ✗ CI.FULL: 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=ZxaIQy+RVf8qTjn1@DUT025-TGLU.fm.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