From: Matthew Brost <matthew.brost@intel.com>
To: "Zeng, Oak" <oak.zeng@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v4 06/30] drm/xe: Simplify VM bind IOCTL error handling and cleanup
Date: Tue, 26 Mar 2024 18:46:56 +0000 [thread overview]
Message-ID: <ZgMYIFKCCP76Nvcn@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <SA1PR11MB69916B4E0EEF26DCADA88E6392362@SA1PR11MB6991.namprd11.prod.outlook.com>
On Mon, Mar 25, 2024 at 10:03:27AM -0600, Zeng, Oak wrote:
> Hi Matt,
>
> This looks like a nice clean up to me. See one comment inline.
>
> > -----Original Message-----
> > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Matthew
> > Brost
> > Sent: Friday, March 8, 2024 12:08 AM
> > To: intel-xe@lists.freedesktop.org
> > Cc: Brost, Matthew <matthew.brost@intel.com>
> > Subject: [PATCH v4 06/30] drm/xe: Simplify VM bind IOCTL error handling and
> > cleanup
> >
> > Clean up everything in VM bind IOCTL in 1 path for both errors and
> > non-errors. Also move VM bind IOCTL cleanup from ops (also used by
> > non-IOCTL binds) to the VM bind IOCTL.
> >
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_vm.c | 60 +++++---------------------------
> > drivers/gpu/drm/xe/xe_vm_types.h | 5 ---
> > 2 files changed, 9 insertions(+), 56 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> > index 0bb807c05d7b..dde777c807cf 100644
> > --- a/drivers/gpu/drm/xe/xe_vm.c
> > +++ b/drivers/gpu/drm/xe/xe_vm.c
> > @@ -769,8 +769,7 @@ static void xe_vm_populate_dummy_rebind(struct
> > xe_vm *vm, struct xe_vma *vma)
> > }
> >
> > static struct dma_fence *ops_execute(struct xe_vm *vm,
> > - struct xe_vma_ops *vops,
> > - bool cleanup);
> > + struct xe_vma_ops *vops);
> >
> > struct dma_fence *xe_vm_rebind(struct xe_vm *vm, bool rebind_worker)
> > {
> > @@ -794,7 +793,7 @@ struct dma_fence *xe_vm_rebind(struct xe_vm *vm,
> > bool rebind_worker)
> > trace_xe_vma_rebind_exec(vma);
> >
> > xe_vm_populate_dummy_rebind(vm, vma);
> > - fence = ops_execute(vm, &vm->dummy_ops.vops, false);
> > + fence = ops_execute(vm, &vm->dummy_ops.vops);
> > if (IS_ERR(fence))
> > return fence;
> > }
> > @@ -2474,7 +2473,6 @@ static int vm_bind_ioctl_ops_parse(struct xe_vm *vm,
> > struct xe_exec_queue *q,
> > if (!last_op)
> > return 0;
> >
> > - last_op->ops = ops;
> > if (last) {
> > last_op->flags |= XE_VMA_OP_LAST;
> > last_op->num_syncs = num_syncs;
> > @@ -2643,25 +2641,6 @@ xe_vma_op_execute(struct xe_vm *vm, struct
> > xe_vma_op *op)
> > return fence;
> > }
> >
> > -static void xe_vma_op_cleanup(struct xe_vm *vm, struct xe_vma_op *op)
> > -{
> > - bool last = op->flags & XE_VMA_OP_LAST;
> > -
> > - if (last) {
> > - while (op->num_syncs--)
> > - xe_sync_entry_cleanup(&op->syncs[op->num_syncs]);
> > - kfree(op->syncs);
> > - if (op->q)
> > - xe_exec_queue_put(op->q);
> > - }
> > - if (!list_empty(&op->link))
> > - list_del(&op->link);
> > - if (op->ops)
> > - drm_gpuva_ops_free(&vm->gpuvm, op->ops);
> > - if (last)
> > - xe_vm_put(vm);
> > -}
> > -
> > static void xe_vma_op_unwind(struct xe_vm *vm, struct xe_vma_op *op,
> > bool post_commit, bool prev_post_commit,
> > bool next_post_commit)
> > @@ -2738,8 +2717,6 @@ static void vm_bind_ioctl_ops_unwind(struct xe_vm
> > *vm,
> > op->flags &
> > XE_VMA_OP_PREV_COMMITTED,
> > op->flags &
> > XE_VMA_OP_NEXT_COMMITTED);
> > }
> > -
> > - drm_gpuva_ops_free(&vm->gpuvm, __ops);
> > }
> > }
> >
> > @@ -2818,8 +2795,7 @@ static int vm_bind_ioctl_ops_lock(struct drm_exec
> > *exec,
> > }
> >
> > static struct dma_fence *ops_execute(struct xe_vm *vm,
> > - struct xe_vma_ops *vops,
> > - bool cleanup)
> > + struct xe_vma_ops *vops)
> > {
> > struct xe_vma_op *op, *next;
> > struct dma_fence *fence = NULL;
> > @@ -2834,8 +2810,6 @@ static struct dma_fence *ops_execute(struct xe_vm
> > *vm,
> > op->base.op, PTR_ERR(fence));
> > fence = ERR_PTR(-ENOSPC);
> > }
> > - if (cleanup)
> > - xe_vma_op_cleanup(vm, op);
>
>
> Now with this cleanup code removed, do you still want to loop all the ops in the list when xe_vma_op_execute failed with error? Should we break and return earlier in this case?
>
Yes, this loop gets rewritten in patch #18 but for this patch to be
correct, lets break the loop on error.
Matt
> Oak
>
> > }
> >
> > return fence;
> > @@ -2858,7 +2832,7 @@ static int vm_bind_ioctl_ops_execute(struct xe_vm
> > *vm,
> > if (err)
> > goto unlock;
> >
> > - fence = ops_execute(vm, vops, true);
> > + fence = ops_execute(vm, vops);
> > if (IS_ERR(fence)) {
> > err = PTR_ERR(fence);
> > /* FIXME: Killing VM rather than proper error handling */
> > @@ -3211,30 +3185,14 @@ int xe_vm_bind_ioctl(struct drm_device *dev, void
> > *data, struct drm_file *file)
> > goto unwind_ops;
> > }
> >
> > - xe_vm_get(vm);
> > - if (q)
> > - xe_exec_queue_get(q);
> > -
> > err = vm_bind_ioctl_ops_execute(vm, &vops);
> >
> > - up_write(&vm->lock);
> > -
> > - if (q)
> > - xe_exec_queue_put(q);
> > - xe_vm_put(vm);
> > -
> > - for (i = 0; bos && i < args->num_binds; ++i)
> > - xe_bo_put(bos[i]);
> > -
> > - kvfree(bos);
> > - kvfree(ops);
> > - if (args->num_binds > 1)
> > - kvfree(bind_ops);
> > -
> > - return err;
> > -
> > unwind_ops:
> > - vm_bind_ioctl_ops_unwind(vm, ops, args->num_binds);
> > + if (err && err != -ENODATA)
> > + vm_bind_ioctl_ops_unwind(vm, ops, args->num_binds);
> > + for (i = args->num_binds - 1; i >= 0; --i)
> > + if (ops[i])
> > + drm_gpuva_ops_free(&vm->gpuvm, ops[i]);
> > free_syncs:
> > if (err == -ENODATA)
> > err = vm_bind_ioctl_signal_fences(vm, q, syncs, num_syncs);
> > diff --git a/drivers/gpu/drm/xe/xe_vm_types.h
> > b/drivers/gpu/drm/xe/xe_vm_types.h
> > index 7ef9e632154a..f097fe318a74 100644
> > --- a/drivers/gpu/drm/xe/xe_vm_types.h
> > +++ b/drivers/gpu/drm/xe/xe_vm_types.h
> > @@ -181,11 +181,6 @@ enum xe_vma_op_flags {
> > struct xe_vma_op {
> > /** @base: GPUVA base operation */
> > struct drm_gpuva_op base;
> > - /**
> > - * @ops: GPUVA ops, when set call drm_gpuva_ops_free after this
> > - * operations is processed
> > - */
> > - struct drm_gpuva_ops *ops;
> > /** @q: exec queue for this operation */
> > struct xe_exec_queue *q;
> > /**
> > --
> > 2.34.1
>
next prev parent reply other threads:[~2024-03-26 18:48 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 5:07 [PATCH v4 00/30] Refactor VM bind code Matthew Brost
2024-03-08 5:07 ` [PATCH v4 01/30] drm/xe: Lock all gpuva ops during VM bind IOCTL Matthew Brost
2024-03-10 17:44 ` Zeng, Oak
2024-03-11 19:48 ` Matthew Brost
2024-03-11 22:02 ` Zeng, Oak
2024-03-12 1:29 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 02/30] drm/xe: Add ops_execute function which returns a fence Matthew Brost
2024-03-22 16:11 ` Zeng, Oak
2024-03-22 17:31 ` Matthew Brost
2024-03-22 19:39 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 03/30] drm/xe: Move migrate to prefetch to op_lock function Matthew Brost
2024-03-22 17:06 ` Zeng, Oak
2024-03-22 17:36 ` Matthew Brost
2024-03-22 19:45 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 04/30] drm/xe: Add struct xe_vma_ops abstraction Matthew Brost
2024-03-22 17:13 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 05/30] drm/xe: Update xe_vm_rebind to use dummy VMA operations Matthew Brost
2024-03-22 21:23 ` Zeng, Oak
2024-03-22 22:51 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 06/30] drm/xe: Simplify VM bind IOCTL error handling and cleanup Matthew Brost
2024-03-25 16:03 ` Zeng, Oak
2024-03-26 18:46 ` Matthew Brost [this message]
2024-03-08 5:07 ` [PATCH v4 07/30] drm/xe: Update pagefaults to use dummy VMA operations Matthew Brost
2024-03-08 5:07 ` [PATCH v4 08/30] drm/xe: s/xe_tile_migrate_engine/xe_tile_migrate_exec_queue Matthew Brost
2024-03-25 16:05 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 09/30] drm/xe: Add some members to xe_vma_ops Matthew Brost
2024-03-25 16:10 ` Zeng, Oak
2024-03-26 18:47 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 10/30] drm/xe: Add vm_bind_ioctl_ops_install_fences helper Matthew Brost
2024-03-25 16:51 ` Zeng, Oak
2024-03-25 19:34 ` Matthew Brost
2024-03-25 19:44 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 11/30] drm/xe: Move setting last fence to vm_bind_ioctl_ops_install_fences Matthew Brost
2024-03-25 17:02 ` Zeng, Oak
2024-03-25 19:35 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 12/30] drm/xe: Move ufence check to op_lock Matthew Brost
2024-03-25 20:37 ` Zeng, Oak
2024-03-26 18:49 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 13/30] drm/xe: Move ufence add to vm_bind_ioctl_ops_install_fences Matthew Brost
2024-03-25 20:54 ` Zeng, Oak
2024-03-26 18:54 ` Matthew Brost
2024-03-26 20:59 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 14/30] drm/xe: Add xe_gt_tlb_invalidation_range and convert PT layer to use this Matthew Brost
2024-03-25 21:35 ` Zeng, Oak
2024-03-26 18:57 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 15/30] drm/xe: Add xe_vm_pgtable_update_op to xe_vma_ops Matthew Brost
2024-03-25 21:58 ` Zeng, Oak
2024-03-26 19:05 ` Matthew Brost
2024-03-27 1:29 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 16/30] drm/xe: Use ordered WQ for TLB invalidation fences Matthew Brost
2024-03-25 22:30 ` Zeng, Oak
2024-03-26 19:10 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 17/30] drm/xe: Delete PT update selftest Matthew Brost
2024-03-25 22:31 ` Zeng, Oak
2024-03-08 5:07 ` [PATCH v4 18/30] drm/xe: Convert multiple bind ops into single job Matthew Brost
2024-03-27 2:40 ` Zeng, Oak
2024-03-27 19:26 ` Matthew Brost
2024-03-08 5:07 ` [PATCH v4 19/30] drm/xe: Remove old functions defs in xe_pt.h Matthew Brost
2024-03-08 5:07 ` [PATCH v4 20/30] drm/xe: Update PT layer with better error handling Matthew Brost
2024-03-08 5:07 ` [PATCH v4 21/30] drm/xe: Update xe_vm_rebind to return int Matthew Brost
2024-03-08 5:07 ` [PATCH v4 22/30] drm/xe: Move vma rebinding to the drm_exec locking loop Matthew Brost
2024-03-08 5:07 ` [PATCH v4 23/30] drm/xe: Update VM trace events Matthew Brost
2024-03-08 5:08 ` [PATCH v4 24/30] drm/xe: Update clear / populate arguments Matthew Brost
2024-03-08 5:08 ` [PATCH v4 25/30] drm/xe: Add __xe_migrate_update_pgtables_cpu helper Matthew Brost
2024-03-08 5:08 ` [PATCH v4 26/30] drm/xe: CPU binds for jobs Matthew Brost
2024-03-08 5:08 ` [PATCH v4 27/30] drm/xe: Don't use migrate exec queue for page fault binds Matthew Brost
2024-03-08 5:08 ` [PATCH v4 28/30] drm/xe: Add VM bind IOCTL error injection Matthew Brost
2024-03-08 5:08 ` [PATCH v4 29/30] drm/xe/guc: Assert time'd out jobs are not from a VM exec queue Matthew Brost
2024-03-08 5:08 ` [PATCH v4 30/30] drm/xe: Add PT exec queues Matthew Brost
2024-03-08 5:42 ` ✓ CI.Patch_applied: success for Refactor VM bind code (rev5) Patchwork
2024-03-08 5:43 ` ✗ CI.checkpatch: warning " Patchwork
2024-03-08 5:44 ` ✓ CI.KUnit: success " Patchwork
2024-03-08 5:55 ` ✓ CI.Build: " Patchwork
2024-03-08 5:55 ` ✗ CI.Hooks: failure " Patchwork
2024-03-08 5:56 ` ✓ CI.checksparse: success " Patchwork
2024-03-08 6:26 ` ✗ 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=ZgMYIFKCCP76Nvcn@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=oak.zeng@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